This content has been marked as final. Show 6 replies
Did you add the jar files for the agent into the classpath?1 person found this helpful
Can you please elaborate on that please. I think I have missed it.
I have the same issue
I have copied the agent.jar, openssosdk.jar files, locale/* and pa/config/* to the appserver/lib/
Restarted both the servers, but I am getting the same result.
This is a very generic error message but it usually means that your agent has not been configured properly and thus cannot contact the and login to the OpenSSO server. There are many causes for this and it depends on what went wrong. Your best bet would be to look under your Agent's config directory and look at the debug logs.
Do you still investigate it? I have ever same error. To solve it, it seems root cause was wrong server url setting for my case.
For my case, root cause was wrong setting of /etc/hosts as default (not discribed the server name on 127.0.01). so I was installing and setting the openam on http://localhost:9080/openam.
so then the agent can not connect to server and resolve the name address, and the problem of "Could not initialize class com.sun.identity.agents.filter.AmFilterManager " happend.
So for resolution, I set /etc/hosts properly as follow.
127.0.0.1 localhost.localdomain localhost sso.server.com
and remove all of openam folder (****/webapps/openam and /root/openam), and re-install openam.war in ****/webapps.
And restart again the setting of openam on http://sso.server.com:9080/openam.
after that, I can resolve it. I hope you also can resolve it.
(ofcourse please modify the server name, IP number and port number as you like)