This blog below outlines the file structure recommended for your plugin for your custom scheduled task within an OIM environment.
1. Name your application
Go into JDeveloper and create a 'new Java Desktop Application'. Then call the name whatever you want. The name of the application within Jdeveloper is not important. You can see I've called it TCScheduledTask. Browse to the OIM_HOME directory and create a 'plugins/TCscheduledTask' directory.
2. Name your project
Within the directory you have created, provide a name for the project. The project name in my scenario is called 'Client' for no particular reason.
3. Configure Java settings
When you click next, ensure you have your source and classes folder within your project directory
4. Use the Ant tool
When left with the option to use a development tool, ensure you select the ant tool and that the build file is build.xml. Place this within your project directory
5. The data structure of the OIM custom plugin
The expected data structure is not particularly clear so let's start off with the build.xml file. If you have set up the application correctly, this file should be already there. This does not require modifying. The build.properties also applies.
The plugin.xml, SampleScheduledTask.java, and OIMScheduledTask.xml are the three files that you have to create. You can download the zip directory (which contains the jar file) here.
Now you have set this up with JDeveloper, you can make data modifications with ease.
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...
Tags
Recent Posts
Monthly Activity
Group by date