January 26, 2017 at 2:31 pm #15535ecervettiParticipant
I had the same problem with Tomcat 9.
I tried Tomcat 8 and I had the same problem.
I tried Tomcat 7 and then it was OK.February 16, 2017 at 12:57 am #15820Peter MajorModerator
FYI this is a Tomcat related issue most likely.
If your json/authenticate call fails with HTTP500 and an empty response, then chances are that the cookie domain you have set up for your OpenAM contains a leading dot ‘.’ character. Just get rid of the leading dot in the cookie domain and things should get better:
ssoadm set-attr-defs -u amadmin -f .pass -s iPlanetAMPlatformService -t global -a “iplanet-am-platform-cookie-domains=foobar.com”February 18, 2017 at 10:15 pm #15870skumlkParticipant
Yes, but unfortunately. Its the only way openam works :(February 18, 2017 at 10:34 pm #15871Peter MajorModerator
Keep in mind that OPENAM-1983 is addressed with 13.5.0, sadly the released community versions are still struggling. :(
March 16, 2017 at 1:56 pm #16295kilakahpParticipant
- This reply was modified 2 years, 4 months ago by Peter Major.
Having the same issue on apache-tomcat-8.5.12.
Changed to apache-tomcat-7.0.75 + reset configuration. Login page started appearing.
Saw similar threads:
https://forgerock.org/topic/opamam-hangs-after-initial-config-with-loading/April 3, 2017 at 8:21 am #16653KishoreDuke007Participant
I have deployed OpenAM-13.0.0 war file into apache-tomcat-9.after completing all custom configuration the login page its keepon loading,login page not displayed.
How to resolve this issue ?May 17, 2017 at 12:47 pm #17379blievensParticipant
Thanks for all info on this thread, it helpt me solve the issue.
I had same problem when running openam from docker context, starting from clean install and after running default configuration setup via web site, go to login screen and it kept loading due to some request errors.
I was using as parent image to start from : tomcat:8-jre8 , after switching to tomcat:8.0.43-jre8 it worked again,
Looking at the current docker images for tomcat : https://hub.docker.com/r/_/tomcat/
I assume it’s caused by a change in tomcat between 8.0 and 8.5 , so probably it’s related to something listed in https://tomcat.apache.org/migration-85.html but did not look further into it.May 25, 2017 at 5:25 am #17471shantnukmrParticipant
After a successful login (using correct username and password) to OpenAm realm, we are greeted with a 404 The page you’re looking for could not be found. while page is being redirected to http://example.openam.com.
We are pointing to openAm configured in remote server and trying to access it through local system. It is working fine for few of my friends but other few we are getting the same problem.
I tried checking openAm log so I could only find the problem is in saying “naming service is not available” but same is working for other users. I tried to reconfigue entire thing from start including maven and my IDE. I am using windows environment. Any help is highly appreciated.March 31, 2018 at 6:40 pm #21366April 3, 2018 at 3:44 pm #21375srkaremParticipant
In case, if you are accessing OpenAM from multiple environments, just clear browser history and try to login.April 4, 2019 at 9:02 pm #25398
You must be logged in to reply to this topic.