Leave a Comment:
7 comments
i installed identity server, web pass, and policy manager.
setup of identity and access system console id also done. Later when i tried to login to access system console, it showed me the error: There was a problem obtaining the user id. one possible reason might be the time difference between the identity and access system console.
But the identity and policy are installed on the same machine.
Any idea on this issue.
ReplyVamshi,
Honestly, I have not seen this error before. But I would check these things :
1. Check if all the installed components are certified.
2. What is the webserver used for webpass and policy manager.
3. see if the webserver httpd.conf file is updated with webpass and policy manager entries.
4. Did you face any issues while setting up identity or access consoles?
5. If not, you can setup the identity and access consoles again (I wrote a post in this forum for this, please check).
6. Did you see any errors while starting access and identity servers? Please check webpass and policy manager logs in TRACE mode.
Thanks,
Mahendra.
“Access Server you specified ins currently down. Pleas check your Access Server.”
The clocks are sync… Still getting that error…
Reply@Jatin,
IS this OAM 10g or 11g ?
If 11g check OAM managed server log file . IF 10g then check Access Server log file and see there are no issues in log file
ReplyJust saw this thread… we are having the same issue but the times are identical between OAM and webgate server. We are running 11g OAM Suite on a RHEL5.6 server. The webgate is installed on Solaris10 with Apache22. We are using Cert Mode for the webgate and have set everything as documented, but are also getting the “Access Server you specified is currently down. Please check your Access Server.”
The access server is running. We have even had this working in the last week and are going through the docs again to make sure we have all the steps properly defined but are hitting this consistently. Nothing unusual is appearing in the oam server log except that it is throwing an error regarding the password for SIMPLE mode — which we are not and never have used.
ReplyNevermind… I was using the wrong aaa*pem files for the importcert command…
Thanks anyway…
Reply