HOW TO provision AD group membership from OpenIDM

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.
June 15, 2018
OpenIDMICFAD-connector
https://technicalconfessions.com/images/postimages/postimages/_453_1_ensure ldap groups is set within sync conf.png

To provide group membership associated to the user, you must reverse that idea and update the account (__ACCOUNT__) and the ICF will then acknowledge if the account has group membership associated to the account. To allow OOTB implementation as well as focusing on connector updates, the AD group membership must be populated during the AD account creation or update but the AD group MUST be associated to the ldapGroup attribute. As highlighted in the first image, I have altered the openidm attribute and mapped it to the ldapGroup attribute.

https://technicalconfessions.com/images/postimages/postimages/_453_2_updating adgroups within PATCH request.png

OpenIDM_AD_Group_Provisioning In the Samples guide it is referenced: sample2c

https://technicalconfessions.com/images/postimages/postimages/_453_3_include ldapgroup in configuration.png

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

https://technicalconfessions.com/images/postimages/postimages/_453_4_reviewing the user based on the context.png

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.

https://technicalconfessions.com/images/postimages/postimages/_453_5_search case.png

To provide group membership associated to the user, you must reverse that idea and update the account (__ACCOUNT__) and the ICF will then acknowledge if the account has group membership associated to the account.

https://technicalconfessions.com/images/postimages/postimages/_453_6_memberOf populated after.png

To allow OOTB implementation as well as focusing on connector updates, the AD group membership must be populated during the AD account creation or update but the AD group MUST be associated to the ldapGroup attribute.

As highlighted in the first image, I have altered the openidm attribute and mapped it to the ldapGroup attribute.

Furthermore, the AD group membership cannot be generated within the sync.conf. As highlighted, you must have the association of the AD group to the user BEFORE the sync.conf association. If you try and associate the attribute during the sync.conf, then you would typically see this stack trace error response

In order to achieve this, you must populate the user object prior to the provisioning. To do this, you can perform this during the user import but you can also perform a PATCH REST API call to OpenIDM user object, as illustrated.

The other thing to note that the provisioner file doesn't necessary accomodate the attribute required to provision AD groups during the provisioning. As highlighted, I included the ldapGroups attribute to the provisioner file.

Please leave a comment - I will always read them :-)

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

ShibbolethSAML

August 7, 2018
Created by: Daniel Redfern
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...

HOW TO provision AD group membership from OpenIDM

OpenIDMICFAD-connector

June 15, 2018
Created by: Daniel Redfern
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...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

ICFIDMOpenIDMOpenICF

November 8, 2017
Created by: Daniel Redfern
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

IDMsync.confforgerockopenidm

November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
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...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
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...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...