
ozcaw (ozcaw) asked a question.
Hi Community, I am trying to integrate OKTA with ServiceNow. I already installed on my Servicenow the OKTA Identity Cloudd API Access and OKTA Activity Pack. But I am unable to sync all my AD groups. Only sync the groups that I create directly in OKTA. My question would be, is there a way to sync my AD groups with out creating those again in OKTA?

A couple of thoughts to consider or try:
Regards,
Edxavier Roberto Cáez
IT Technical Specialist II | Information Technology
Retail
Brookfield Properties
350 N Orleans St. Suite 300, Chicago, IL 60654
T 1.855..447.4457<tel:1.855..447.4457>
edxavier.caez@brookfieldpropertiesretail.com<mailto:edxavier.caez@brookfieldpropertiesretail.com>
www.brookfieldpropertiesretail.com<http://www.brookfieldpropertiesretail.com/>
Brookfield
Properties
[http://signature.ggp.com/test/images/twitter.png]<https://twitter.com/Brkfldproprtl>
[http://signature.ggp.com/test/images/linkedin.png]<https://www.linkedin.com/company/brookfield-properties-retail/>
[http://signature.ggp.com/test/images/facebook.png]<https://facebook.com/BrookfieldPropertiesRetail/>
[http://signature.ggp.com/test/images/instagram.png]<https://www.instagram.com/brookfieldpropertiesretail/>
"Verify that the group you pushed is not the same one you used to assign and provision users to the app. Using the same Okta group for assignments and for group push is not currently supported."
Tim, can you or someone help to explain why we should not use the same group for app assignment and push group? I heard that there is a potential race condition. However, I still don't quit understand how a race condition can occur.
I have used the same group for app assignment and push group without any issue so far.
if there is issue when using the same group, what is the work-around? Do we need to have two different groups (i.e. 1 for app assignment and push group) even when the group memberships for both are the same?
I'll admit that I don't know the details, but I can see how a race condition might occur if you were using the same group for both: what if the Push Group is trying to push a newly-assigned user downstream before the assignment to its application in Okta and the subsequent provisioning is completed? The Group Push would fail because that user doesn't yet exist in the app.
EDIT: so yes, the workaround is two groups, even if the membership is the same.