This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Issues using a Wildcard SSL Certificates for PAM

Keng over 2 years ago

Hi,

I am actually disappointed that even latest PAM 4.1 we are still unable to use a Wildcard SSL Certificates.

With the browsers upgrade speed, the PAM self signed Certificate is obviously causing an issue. Able to access it 1 month ago. But with recent browser update unable to access.

I had filed SR since PAM v 3.7 and onwards, create Enhancement Requests in both Old and New Idea Portal since then.

And there is no workaround provided while waiting for Wildcard Cert support.

Anyone have any workaround ?

0 Norbert Klasen over 2 years ago

Currently, you need to generate a key pair and certificate request in PAM, have it signed by your CA and then import the certificate: https://www.netiq.com/documentation/privileged-account-manager-41/npam_admin/data/hosts_cert_req.html
Cancel
Vote Up 0 Vote Down

Cancel
Suggested Answer

0 Keng over 2 years ago

Support had confirmed Wildcard Certificate support is in PAM 4.2 in Q1 2022.
Cancel
Vote Up 0 Vote Down

Cancel
0 Marko Selan over 2 years ago in reply to Keng

4.2 is out, but wildcard Certificate support is nowhere to be found.
Cancel
Vote Up 0 Vote Down

Cancel
0 Keng over 2 years ago in reply to Marko Selan

Now Support had reverted that it is targeted as the patch after PAM 4.2 is released.

Sigh....
Cancel
Vote Up 0 Vote Down

Cancel
0 Marko Selan over 2 years ago in reply to Keng

4.2.0.1 is out and ... nope
Cancel
Vote Up 0 Vote Down

Cancel

Menu

PAM User Discussions

Issues using a Wildcard SSL Certificates for PAM

Suggested Answer

Resources