Microsoft Windows
Sun Solaris
Check Point Firewall
Unable to request Certificate for a Check Point Firewall through PKCS10 request in RSA Certificate Manager.
When submitting a PKCS10 request from Check Point Firewall through the enrollment page, the following error appears after clicking the Submit button:
!PKCS10Parse(): [XrcDECODINGFAILURE] unable to complete decoding operation. XudaParsePKCS10Request(): [XrcDECODINGFAILURE: unable to complete decoding operation]
When generating the request in Check Point Firewall, there is an option to include alternative name information.
ex: IP address. You select the checkbox and the option you require. This information is put in as part of the subject Alternative Name.
When using an ASN.1 Editor to view the request, the Subject Alternative Name portion appears as follows:
243 31 22: SET {
245 30 20: SEQUENCE {
247 30 18: SEQUENCE {
249 06 3: OBJECT IDENTIFIER subjectAltName (2 5 29 17)
254 01 1: BOOLEAN FALSE <----------------------
257 04 8: OCTET STRING
: 30 06 87 04 3E B0 3F 28
The line that includes BOOLEAN FALSE should not be included in that part of the request as it is an invalid format. This causes the decoding failure.
Related Articles
Some buttons in "Cloud Authentication Service Configuration" are not worked with Internet Explorer in Authentication Manag… 4Number of Views Explaining Aveksa Security Entitlements (SecurityContext.csv) in RSA Governance & Lifecycle 23Number of Views How to retrieve the CT Server info enter into RSA Federated Identity Manager (FIM) GUI within Custom Plugins 2Number of Views Identity Confidence Score API 7Number of Views How to Install a Third Party Certificate into enVision 13Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide User Application Portal The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn… How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console Unable to Resolve User by Login ID and/or Alias or Authenticator Not Assigned to User When Attempting to Authenticate via …