Hi! Yes - we've had issues recently with assertion mapping between okta and Khoros... so thats why we've changed tactic and gone down the route of utilising Okta Workflows to assign the user to a role via API and assign the badge in khoros off that (we could use this to push/update the data in the khoros profile too) but utilising oktagroups=khoros role simplifies most badges. This avoids relying on Khoros support to create the custom profile fields. The process is repeatable and managed by Okta Group membership. Which also makes it easy to trigger from external sources. Eg: Learning center webhook upon course completion. Triggers flow which checks if there is a corresponding okta group and adds the user if there is. Then the api adds the role, khoros adds the badge.
... View more
