February 5, 2016 at 10:56 am #7551Rajesh RParticipant
@amit-gupta06 By the way, while testing it, you could clear the cookie on your browser and restart it. I’m also assuming that the domainname and FQHN used by OpenAM is all configured properly.February 5, 2016 at 11:10 am #7552
First Time I logged in and logged out immediately within 10 secs without performing any action and just restarted my machine. Hence I didnt do anything in the ‘Authentication’ section of your Top Level Realm.
The Authentication Log file is attached at:
I also tried loggin in with username: demo and password ‘changeit’. Even that is giving same error i.e. bad combination of username / password.
I have tried clearing all the cookies and history from the browser and restarted it but still receiving the same error.
Amit GuptaFebruary 5, 2016 at 12:49 pm #7554
I logged in only for few seconds and then logged out. Then restarted my machine and again tried loggin in.
Hence I did not do anything in the “Authentication’ Section in the Top Level Realm.
Also tried logging with user ‘demo’ and password ‘changeit’; it is giving me same issue as user ‘amAdmin’ i.e. authentication failure.
I even tried clearing the cookies and restarting the browser it is still showing me same error.
Log file contents while I try to Log in is available at below pastebin URL:
http://pastebin.com/UNhzXCL6February 7, 2016 at 10:09 pm #7579
You should have a look at the debug logs (Authentication file to be specific). The log folder only contains audit logs which are not that helpful for diagnosing issues.February 8, 2016 at 7:05 am #7587
I am seeing similar errors as I was observing in my previous installation as well. The Authentication Debug Logs are attached at the below pastebin URL:
I am stuck with Authentication issues and unable to proceed with my trial deployments …February 9, 2016 at 1:34 am #7623
At this stage debugging this with an IDE would sound like the best way forward, though I appreciate that may not be the easiest thing to do.
Just to make sure: you haven’t deployed a policy agent on the very same container as runs OpenAM, right?February 9, 2016 at 5:41 am #7628
No I haven’t deployed any policy agent yet.February 9, 2016 at 11:36 am #7631Rogerio RondiniParticipant
Could you share IdRepo, CoreSystem, and Configuration debug files ?
Rogerio RondiniFebruary 9, 2016 at 1:27 pm #7641February 12, 2016 at 9:36 am #7791
The logs aren’t telling us a lot unfortunately. What seems to be happening is that at startup time OpenAM creates an admin session that does not have a required session property, and that results in an NPE within AuthSPrincipal. Why that session does not have the session property is a mystery though. :(February 12, 2016 at 9:42 am #7792
Yes Even I am trying to figure out the issue. Unfortunately I have tried setting up OpenAM 3 times and every time I run into some or other issue. Not sure if I am doing some other basic mistake.
Also is it possible to setup OpenAM on Windows Platform ? I have never tried that but can give that a try as well.
Amit GuptaFebruary 12, 2016 at 10:53 am #7793Rajesh RParticipant
@amit-gupta06 Indeed, it’s quite annoying not to get the OpenAM Installation working. But shouldn’t be that hard, I believe. ForgeRock OpenAM can be installed on Windows platform as well. So you can give it try.
I’m sure you might have seen the ‘Getting Started’ Documentation on OpenAM, but if you haven’t it’s at the link below:
Referring to the document above, things should just work fine. Worthwhile giving it a try again. For your quick reference, here are the steps:
– Make sure the FQHN is added to the /etc/hosts file of your machine (or a DNS in place)
– Install Java, if not already done (version 7, 8)
– Install Tomcat
# unzip apache-tomcat-22.214.171.124.zip
# mv apache-tomcat-126.96.36.199.0 /tomcat
# chmod +x /tomcat/bin/*.sh
– Create a setenv.sh file to set JAVA_HOME / CATALINA_OPTS
– Copy the said file to the /tomcat/bin directory
– Copy the OpenAM binary to the Tomcat Container
# cp OpenAM-13.0.0.war /tomcat/webapps
– Start Tomcat
Access the following URL and complete the OpenAM Configuration
For keeping it simple, you could opt the Default Configuration and proceed with the setup
We really hope you get this working soon and explore many other interesting features of OpenAM.November 16, 2016 at 11:23 pm #14325rmParticipant
Was this ever resolved, I am having the same issue. I am new to openAM/January 6, 2017 at 6:09 pm #15204skumlkParticipant
I came up with this same problem. In my case, I tried in a windows 10 machine. And I only get this error when I tried to login openam through http://openam.example.com:8080. I set openam.example domain to localhost in the etc/host file in windows. But later I reinstalled openam and configured it with localhost, then it works perfectly.
I found something intersting when I installed openam with openam.example.com domain. I got couple of json errors and a 404 error for the file http://openam.example.com:8080/openam/XUI/locales/en-GB/translation.json?v=13.0.0. Then I changed this url to http://localhost:8080/openam/XUI/locales/en-GB/translation.json?v=13.0.0, now I get a HTTP 500 – AMSetupFilter.doFilter error.January 9, 2017 at 12:03 am #15217
@skumlk you should not install the server using “localhost”:
You must be logged in to reply to this topic.