I followed the readme, however on first access to Alfresco I get a
java.lang.NoClassDefFoundError: Could not initialize class com.iplanet.services.naming.service.NamingService
and on refreshing the page I get another exception
java.lang.NoClassDefFoundError: Could not initialize class com.iplanet.dpro.session.Session
NamingService is not present in the opensso client jar file but the Session class is present in it. Any ideas what might be causing this or which jar files need to be included for the NamingService class?
Also I wasn't sure which AMConfig.properties file needs to be edited. I found one in in <webapps>/opensso/WEB-INF/classes/AMConfig.properties but that did not have a property corresponding to Opensso server home directory
You have to change the IP, port, and password to reflect your OpenSSO server. Also, in alfresco web.xml, pay attention to the filter property "opensso.url", that must point to the OpenSSO web application.
No changes are required to OpenSSO web application files since this is a client deployment that will are doing.
– Gustavo Nalle Fernandes g.fernandes at sourcesense.com
The com.sun.identity.agents.app.username and com.iplanet.am.service.password are the credentials of the Default Policy agent. They're used by the opensso client to read OpenSSO data remotely.
Thanks for the pointer on the AMConfig.properties.
I had more errors with this AMConfig.properties and the exception specifically said that I need to check the username and password in AMConfig. As it turns out this exception message is less than helpful. Enabling debug message in AMConfig.properties finally pointed me in the right direction.
In my case, I had tomcat running alfresco and opensso as a non root user in port 8080 and an iptables rule to route connections to the box on 8080 to port 80. The client was using http://localhost:80/opensso to do its SSO token creation and validation and was getting connection refused errors. So I had to add another iptables rule to make the 80->8080 port forwarding within localhost.
