Subject Alternative Name is not getting recognized after providing CSR in Service Portal catalog item while creating new Server Certificate request. - Known Error

Subject Alternative Name is not getting recognized after providing CSR in Service Portal catalog item while creating new Server Certificate request. Description Subject Alternative Name is not getting recognized after providing CSR in Service Portal catalog item while creating new Server Certificate request. Script include SNC.DiscoveryCertificateUtil is not able to recognize the Subject Alternative Name (SAN) in cert. This issue getting triggered when we have work the word "critical" within the X509v3 Subject Alternative Name "X509v3 Subject Alternative Name: critical"

Steps to Reproduce

1. Go to Service Portal and select Request Something 2. Go to catalog item for Certificate 3. Fill in form fields and choose CSR with critical included like below: "X509v3 Subject Alternative Name: critical" 4. You should see Common Name populated but Subject Alternative Names is empty.

Workaround Issue in java code for CSR's having "X509v3 Subject Alternative Name: critical". Since the issue is in java layer, we cannot provide an update set with a fix. For now one workaround would be to use CSRs without "X509v3 Subject Alternative Name: critical"

Code fix is provided as part of problem record PRB1520046 in "SR - ITOM - Certificate Inventory and Management 202111"