<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000AH9sStCQJOkta Identity EngineWorkflowsAnswered2024-11-29T16:38:48.000Z2024-11-14T14:40:55.000Z2024-11-29T16:38:48.000Z
Okta Workflow to remove user from a group after their next logon?

We're using JAMF Connect, and have new users set to change their password at first logon, if users are prompted for JAMF MFA they're not getting a change password prompt so we've put them in a No MFA group for the first logon.

 

Can we automate a Workflow to remove them from the No MFA group after first logon?


  • TimL.58332 (Workflows)

    @User16880603318257874714 (Customer)​  -- I am not entirely certain which Event you are seeing triggered in this scenario. However, I am going to assume it is: user.authentication.sso

     

    As Diana mentioned previously having an event hook against user.authentication.sso is typically not considered a good use case as it is extremely busy event. However, if this is the event AND it is limited to a specific condition like JAMF it might be viable using Event Hook Filtering.

     

    With Event Hook Filtering enabled (Pretty sure it is still EA) it provides an additional step in Workflow > Event Hooks creation process that allows a limited subset of Event Attributes to be filtered against allowing you to limit the event firing to a subset of the total.

     

    So for example user.authentication.sso you could limit it to a specific target.id (so a specific application Id) and ONLY if it was a successful login. There are possibly a few other of the filterable attributes that could be leveraged to further narrow it.

     

    This would at least limit it to SSO connects to a specific application and not ALL applications greatly reducing the repeated processing.

     

     

    Expand Post
    Selected as Best
  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hello @User16880603318257874714 (Customer)​ , thank you for contacting Okta Community.

     

    I've brought up your question to our specialized team. It appears that this will be an expensive workflow that would trigger on every sign-in, for all users: User Signed In Attempt event, then you would have to run the Get users Groups, and if "no MFA" run the "Remove user from group".

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
  • TimL.58332 (Workflows)

    @User16880603318257874714 (Customer)​  -- I am not entirely certain which Event you are seeing triggered in this scenario. However, I am going to assume it is: user.authentication.sso

     

    As Diana mentioned previously having an event hook against user.authentication.sso is typically not considered a good use case as it is extremely busy event. However, if this is the event AND it is limited to a specific condition like JAMF it might be viable using Event Hook Filtering.

     

    With Event Hook Filtering enabled (Pretty sure it is still EA) it provides an additional step in Workflow > Event Hooks creation process that allows a limited subset of Event Attributes to be filtered against allowing you to limit the event firing to a subset of the total.

     

    So for example user.authentication.sso you could limit it to a specific target.id (so a specific application Id) and ONLY if it was a successful login. There are possibly a few other of the filterable attributes that could be leveraged to further narrow it.

     

    This would at least limit it to SSO connects to a specific application and not ALL applications greatly reducing the repeated processing.

     

     

    Expand Post
    Selected as Best
This question is closed.
Loading
Okta Workflow to remove user from a group after their next logon?