<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
0D54z0000ABuQwpCQFOkta Identity EngineWorkflowsAnswered2024-07-31T16:27:41.000Z2024-07-08T15:43:03.000Z2024-07-31T16:27:41.000Z

JordenT.25841 (Customer) asked a question.

Pulling a random user in a workflow

I am trying to work on my own version of a push phishing workflow as we only have 5 workflows, in the process of getting more. We have about 950 users and I initially set it to pull users from a group, assign an integer then pull a random integer and find the user. However, this will always just pull the first 200 users added into Okta, so I would be missing the other 750 users. According to Okta, if the query is left blank it pulls a random user but in my case it doesn't. Any other ways to pull a random user or randomize the user list coming from my group? I've tried several different APIs but they will always pull the same user.


  • TimL.58332 (Workflows)

    @JordenT.25841 (Customer)​  -- Calling the Okta API's is going to pull the first page of results based on the request to the API. The Okta Users API has a maximum (and default) page size of 200. You can utilize supported request params to change the returned results.

     

    I am not really understanding the "random integer" thing. Users don't have any sort of integer property. You could definitely create a custom property that contains an integer then search for users on that property with a matching value. Users API documentation can be found here:

     

    https://developer.okta.com/docs/reference/api/users/

     

    Alternatively, since you have under 3500 records you could just write all users to a Workflows table. Then "Search" the table getting a results of all users then randomly pull a 0 -> max int value place in the returned list to obtain your "random" user (List - AT -> int value). This "Table" setup would require 2 active flows but they only need to be "active" to populate the table initially.

    Expand Post
    Selected as Best
  • TimL.58332 (Workflows)

    @JordenT.25841 (Customer)​  -- Calling the Okta API's is going to pull the first page of results based on the request to the API. The Okta Users API has a maximum (and default) page size of 200. You can utilize supported request params to change the returned results.

     

    I am not really understanding the "random integer" thing. Users don't have any sort of integer property. You could definitely create a custom property that contains an integer then search for users on that property with a matching value. Users API documentation can be found here:

     

    https://developer.okta.com/docs/reference/api/users/

     

    Alternatively, since you have under 3500 records you could just write all users to a Workflows table. Then "Search" the table getting a results of all users then randomly pull a 0 -> max int value place in the returned list to obtain your "random" user (List - AT -> int value). This "Table" setup would require 2 active flows but they only need to be "active" to populate the table initially.

    Expand Post
    Selected as Best
This question is closed.
Loading
Pulling a random user in a workflow