<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
0D54z00008HyXSWCA3Okta Identity EngineWorkflowsAnswered2022-10-28T21:29:07.000Z2022-10-28T17:59:53.000Z2022-10-28T21:29:07.000Z

JacksonK.52224 (Customer) asked a question.

Sending a temporary password in an email to a recently activated user

Hello there,

 

I am trying to create a workflow in which when a user is activated, the password would be set and reset for that user. And then the point being it should take the temporary password Okta created and send it via the email template based on what's in compose to the user's "secondaryemail" which is their personal email, to log in to Okta.

 

We don't want to have the URL link sent to the new user, we want the user to just head to our okta platform and sign in with their username and temp password. This is a limitation with the way our chrome is set up (we don't allow people to sign in with their personal accounts)

 

However, when "reading" the user's attributes, it won't pick up the temporary password created as the field is a T/F value.

 

Is there a way to have this workflow read the temporary Okta password created and send it to the user?

 

/help/servlet/rtaImage?refid=0EM4z000005HlIv


  • TimL.58332 (Workflows)

    @JacksonK.52224 (Customer)​ 

     

    Hello,

     

    The "password" value you are specifying is just a parameter indicating that a password is being used for the user account. It would be incredibly unsecure to allow passwords to be retrieved in plain text by anyone including an Administrator.

     

    Based on the API documentation:

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

     

    I don't think your use case is achievable on "Activation". It definitely would be achievable if the flow was "Creating the user with a password" so the password is known and could then be later used in the flow to send an email to the specific email address.

     

    If you want to determine feasibility of your use case Lifecycle Management is probably a better location to ask this question as you are not having an actual issue with the Workflows product. If it is possible, and you can determine the series of API calls / Actions that would be required to make it work this then could likely be automated in Workflows.

    Expand Post
  • JacksonK.52224 (Customer)

    Gotcha. I think we're gonna go with an immediate solution, which is to activate the account after it's created and send an email that should go to their "secondary email" address for them to click the link to activate.

     

    image

    Expand Post
This question is closed.
Loading
Sending a temporary password in an email to a recently activated user