It appears that Aspose.Page is not FIPs compliant. We are getting an exception related to System.Security.Cryptography.MD5CryptoServiceProvider
. I see other older items on FIPs compliance so it seems like perhaps the intent is that it is FIPs compliant.
Are you using the latest version of the API? Can you please share your sample code snippet and the sample file for our reference so that we can test the scenario in our environment and address it accordingly?
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): PAGENET-771
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.