-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 6.5.1, 7.0.0
-
Component/s: documentation
-
Labels:
-
Environment:AM 6.5.1
-
Sprint:AM 2019.7 - Lighthouse
-
Story Points:0.5
-
Needs backport:No
-
Support Ticket IDs:
-
Needs QA verification:No
-
Functional tests:No
-
Are the reproduction steps defined?:No (add reasons in the comment)
Bug description
https://backstage.forgerock.com/docs/am/6.5/install-guide/#cts-openam-gui
This section needs a strong warning, that if you configure this incorrectly, you will be unable to access the AM console.
How to reproduce the issue
https://backstage.forgerock.com/docs/am/6.5/install-guide/#cts-openam-gui
- It should be assumed but we need to warn that If using LDAPS to configure Certificates, The certificate must match the hostname
- Bind Account should be checked as well
Expected behaviour
Documentation may want to warn to have a backup available.
Current behaviour
Multiple customers getting stuck with no console access
Work around
Edit dn: ou=server-default,ou=com-sun-identity-servers,ou=default,ou=GlobalConfig
,ou=1.0,ou=iPlanetAMPlatformService,ou=services,dc=openam,dc=forgerock,dc=org
in the configuration store to remove the improper configurations
org.forgerock.$className.java
...