SSL certificate not importing

[fsadoon]

DO NOT FILE AN ISSUE FOR HELP OR TO ASK QUESTIONS. This issue system is not for help requests and such issues will be deleted.

Instead, please ask for help on the PWM-General Google Group. If your not sure, it's better to ask on the pwm-general group before opening an issue here.

Describe the bug A clear and concise description of what the bug is. when importing SSL KEY it doesn't work and doesn't appears

To Reproduce Steps to reproduce the behavior: N/A

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen. The Key to Appears in imported keys Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[jrivard]

Are you using the latest docker container snapshot of PWM 2.0-SNAPSHOT? Please post container logs.

[fsadoon]

hi there, yes am using the latest docker container PWM 2.0-SNAPSHOT,

logs are attached

Note : i removed my configuration and ran the container from scratch

pwm.txt

[fsadoon]

i tried Windows/Ubuntu and same is happening

[jrivard]

This container log doesn't have a configuration, thus it's using the default self-signed HTTPS cert. Please attach a log of the container starting with an HTTPS certificate configured.

[fsadoon]

do you mean that i need to run the docker image with my cert ? like : docker run -v /host/path/to/certs:/container/path/to/certs -d IMAGE_ID "update-ca-certificates"

[fsadoon]

• what if i want to deploy it on tomcat directly.. it still not taking the cert

[jrivard]

I've been able to reproduce an issue where the configeditor UI is not properly saving the cert during the import process. I think that's what you were originally reporting.... Standby for a fix.

This issue only affects the docker container and onejar distro. If you use the WAR file your on your own for configuring the HTTPS certificate, it won't be a config option in the configeditor.

[fsadoon]

Yup .. it works with the WAR file , struggled little bit to deploy it but eventually it works .. Appreciate your effort

[fsadoon]

Yup it works with the WAR file, struggled little bit in the deployment but eventually it works ..

Appreciate your effort

[fsadoon]

BTW, in the war file .. i can use the search bar to get the HTTPS option :) so you might want to disable it

[jrivard]

fixed in db7c2ee968d0657f25dbf552bc942a06f6fc9ee4