I have recently located the e-mail templates and parameters required for OIA once a certification has been created
Scenario 1 - No RBACX user
The user 'COOLUSER' has the a manager 'COOLMANAGER' assigned to the globaluser. The manager has an e-mail address assigned to the globaluser. No RBACX user was created on this point.
Result
This creates the rbacx security access control manager (RBACX UN) with an e-mail address of COOLMANAGER@OIA.COM. A certification is also created
Scenario 2 - Manager UN (case sensitivity)
This time the certification creation is attempted though the manager field assigned to the user globaluser does not match (case sensitive) with the globaluser manager.
Result
The certification is not created because of the case sensitive.
Scenario 3 - case sensitive manager
The workflow manager now matches the case sensitive manager in the globaluser
Result
The certification is created and the e-mail is created for the manager
Scenario 4 - Existing RBACX UN for Manager
In this scenario, the manager's RBACX UN already exists, though the e-mail does not match the manager's globaluser.
Result
The certification is created even though the Manager's RBACX UN does not match the managers globaluser UN. Furthermore, the e-mail address does not get updated. The e-mail is sent to the Manager globaluser UN and not the managers RBACX UN.
Conclusion
After these investigations, it's clear that you must ensure you're using the following rules:
- The 'Manager' field assigned to the globaluser exists to create a certification
- The 'Manager' field must match the manager globaluser identity to create a certification
- The 'Manager' field assigned to the globaluser is case sensitive
- The 'Manager' field is not case sensitive regarding the relationship between the manager's globaluser and the Manager's RBACX username
- The e-mail address used for e-mails notifications is taken from the manager's globaluser and not the manager's RBACX user
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...