
abcn0 (abcn0) asked a question.
We have a SCIM connector in Okta for legacy API and database systems. We noticed that our Okta Push Group connector is sending the group name and not sending the users within the group. We spoke with Okta, and they said it works to send the members as well.
However, we can't find a way to do this. While testing, we placed the same group within tasks, and then I envy the members of that group also contained in the Okta Push Group. But this is a problem, because in Okta's architecture, you can't use the same group for both, as it will cause conflicts in large systems and isn't good practice. Can anyone confirm and guarantee that it actually sends the members in the Okta Push Group? I want to be sure it does so we don't waste effort trying to fix this in the connector and avoid it being a connector issue. It would be terrible to have duplicate groups—one for assignment and one for push group—and create rules to populate them as Okta instructed. This is terrible for legacy systems, as it multiplies the number of groups and our time effort.

Hello @abcn0 (abcn0) Thank you for posting on our Community page!
For your scenario unfortunately that is correct, in order for Group Push to work as intended you will need 2 groups, 1 for assignment to the application and a different one for Group Push.
Additionally you can add an Idea on our Ideas section for a change that this behaviour can be improved in the future.
https://ideas.okta.com/
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Just released: More Okta Community badges just added.