<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
0D54z00007UhWZVCA3Okta Classic EngineAdministrationAnswered2024-04-12T22:29:41.000Z2022-03-09T19:26:11.000Z2022-03-10T16:49:58.000Z

MatthewW.69352 (Customer) asked a question.

User activation procedure when dealing with different identity provider

Hello

My organization plans to import users via workday. We are using workday as our profile source. Then authenticate to okta via the Azure directory. We have it so that the user has to use the same password for okta as they do for Azure.

 

My questions are below.

 

1. Since the users are authenticating through Azure, is there a way to negate the typical ok user creation process? Specifically, not sending out the standard activation email? I only ask because it seems silly for users to set up by okta password and security question that they will never use. After all, they will use the one for their account in Azure.

 

2. It is possible to send out different emails based on the domain. For example, sending out activation emails for users that use an outside organization domain like Gmail.com versus an organization domain like @company.org?

 

3. Is it possible to send out activation emails based on a user attribute? For example, only send out an activation email if the title attribute designates a person as a supervisor?


This question is closed.
Loading
User activation procedure when dealing with different identity provider