Error when provisioning users from AD in okta

Loading

Skip to Navigation Skip to Main Content

Search

Search

Select Language

0D54z0000A5s64kCQAOkta Classic EngineAuthenticationAnswered2024-04-30T17:49:57.000Z2024-04-12T16:51:16.000Z2024-04-30T17:49:57.000Z

User17129402037004725770 (Customer) asked a question.

April 12, 2024 at 4:51 PM

Error when provisioning users from AD in okta

I have two types of user to access an application and carry out the authentication process, the first is userID@mydomain.com, with these I have had no problems when re-provisioning, carrying out some tests with very old AD users, they use first name last name, to perform authentication. Since it has a space in the middle of the two parameters (first name last name), this is generating an error when provisioning because it does not comply with the format, is there a way to resolve this?...

Authentication

Top Rated Answers

Mihai Negoita - Okta (Okta, Inc.)
2 years ago
Hi @User17129402037004725770 (Customer) Just for clarity, default attributes are not replaceable with custom ones.
What I meant was not "custom attribute mapping" , instead "custom attribute mapping" - as in setting up custom value for the incoming attribute via custom expression. As opposed to the default selectable options in the AD import settings:

Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Expand Post
Selected as Best

All Answers

Mihai Negoita - Okta (Okta, Inc.)
2 years ago
Hi @User17129402037004725770 (Customer) , Thank you for reaching out to the Okta Community!

Depending on the use case, you can look into changing the username restrictions or perhaps implementing a custom attribute mapping for the username to something covers your requirements. The following documentation will offer more insight into the matter:

Username restriction

Change the Login Username format for AD

Attribute Mappings

Modify attributes with expressions

If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.

Hope my answer helps!

--
Help others in the community by liking or hitting Select as Best if this response helped you.
Expand Post
User17129402037004725770 (Customer)
2 years ago
Hi @Mihai Negoita - Okta (Okta, Inc.) , Thanks for your help, I need to know. Is it possible that we are implementing a custom attribute and a default attribute at the same time?
Expand Post
- Mihai Negoita - Okta (Okta, Inc.)
  2 years ago
  Hi @User17129402037004725770 (Customer) Just for clarity, default attributes are not replaceable with custom ones.
  What I meant was not "custom attribute mapping" , instead "custom attribute mapping" - as in setting up custom value for the incoming attribute via custom expression. As opposed to the default selectable options in the AD import settings:
  
  Regards.
  --
  Help others in the community by liking or hitting Select as Best if this response helped you.
  Expand Post
  Selected as Best

This question is closed.

Recommended content

Forum

Error When Configuring Azure AD as IDP in Okta

Forum

Error when install Ad agent in Window Server 2008 R2 (VMWare)

Forum

AD Accounts Disabled After Activation – Error “Matching User Not Found”

Forum

O365 User Provisioning when domain is not in O365

Loading

Error when provisioning users from AD in okta