When deploying the agent within your local environment or deploying from eclipse, you'll likely come across the 'java.lang.ClassNotFoundException: com.sun.identity.agents.filter.AmAgentFilter' error when compiling or deploying to a particular server.
SOLUTION #1: Use Maven and OpenAM
The reason for this error is because you're not including the jar files within the classpath. One way is to use the maven dependency within your pom.xml The information needed to do this can bere located by clicking on the, Using Maven and OpenAM
SOLUTION #2 Include jar files within lib
This is a simplified option if you're experiencing issues with solution #1, such as firewall restrictions or whether you're not using maven. Assuming you're using eclipse as your ID, you can populate the lib directory with the jar files by simply copying over the libs within your workspace. These lib files can be located as part of your agent download (though they are actually within your mod_openam.so file). The easiest way extract the lib files is to install the agent, of which the lib files can be located within the forgerock directory (which is typically created on the same location as your container called forgerock/j2ee_agents directory) After you've done that, you need to click project -> clean as shown in the diagrams
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...
Tags
Recent Posts
Monthly Activity
Group by date