The easiest way add users through a GUI within OID would be through ODSM.
Assuming you've already followed the blog, Start up Oracle Identity Directory 11.1.1.6, you would already have OID and ODSM up and running with a connection pre-defined.
1. Once you've logged into ODSM, click on Data Browser.
2. In the data tree, click Create a new entry.
3. To add a user, you must search for the inetOrgPerson object class.
4. Within the Parent of the entry field, select the cn=Users located within the dc=.
5. Click next and you will be taken to the Mandatory Properties dialog.
6. within in the cn, enter the full name of the User.
7. Enter the surname within sn textbox.
8. Enter cn within the Relative Distinguished Name.
9. Click next and then click finish.
You should now be able to see the user you've just created by navigating through the data tree.
Greating a new Group
You can create groups by using the same way as creating a user within OID. The difference is the object class
In creating groups, the object class is actually called groupOfNames
You can now see from within the data tree that a group has now been created.
Additional Attribute Values
OID also allows you to populate further information regarding that unique CN by clicking on the attributes tab. There's many to choose from though in this screenshot I populated a password within the password field (with the intention of integrating this in later blogs)
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...