Once the OPAM installation was made, I noticed within the OPAM GUI the following error...
This role-type is not authorized to change server settings. Please contact the Administrator.
I was also noticing the following error within the weblogic logs:
<Mar 7, 2013 8:03:08 PM EST> <Error> <com.oracle.ovd.arisid.IdentityStoreConfig> <BEA-000000> <Failed to get IdentityStore properties from OPSS - org.openliberty.arisid.IGFException>
java.lang.NullPointerException
at com.oracle.ovd.arisid.ArisIdStackProvider.doSearch(ArisIdStackProvider.java:259)
at org.openliberty.arisid.Interaction.doSearch(Interaction.java:1379)
After investigating this, I came to realize that OPAM installation must reside on a separate domain of the SOA deployment. (Obviously this would of been helpful if this was mentioned within the Oracle installation guide!). click here to see the video on how to install OPAM on a Oracle Linux 64bit environment.
Secondly, you need to give Weblogic user the necessary permissions to make the changes. Log in to work with the WebLogic Server domain by accessing the http://hostname:port/console path.
On the left hand side, click Security Realms.
Click on realm, unless you've changed it in the past, it will be myrealms
Click on Users and Groups tab and click the weblogic user
Click on Groups and add OPAM_APPLICATION_CONF and click save
Restart the weblogic server and click on the OPAM URL. You will now be able to change the settings within OPAM
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
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
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...