Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

Scandinavian character are not accepted to be saved in Identity repository for last name

alexandrupop
New Contributor
New Contributor

Hi,

Are there any restrictions in saving user details like Last Name with Scandinavian characters in UI under Identity repository?

At least I see the User regex validator is set to accept it. 

alexandrupop_0-1692954526845.png

Could it be that this is restricted by Saviynt by default?

 

 

 

7 REPLIES 7

pmahalle
All-Star
All-Star

@alexandrupop Which connector you are using to import the users?


Pandharinath Mahalle(Paddy)
If this reply helps your question, please consider selecting Accept As Solution and hit Kudos 🙂

alexandrupop
New Contributor
New Contributor

Hi,

It's a a GoogleApps connection.

 

Br,

Alexandru

wilmaj
New Contributor
New Contributor

Hi, any updates on this? Thanks!

nimitdave
Saviynt Employee
Saviynt Employee

@wilmaj 

1. Scandinavian characters are allowed in lastname

2. The above regex config in evaluated when users lastname is updated/created from UI only.

3. Please elaborate on the issue, as in do you see question mark (?) instead of Scandinavian character ,or its getting skipped or its getting converted to equivalent English characters.

4. Also , are you using any pre-processor/inline processors while user import?

5. Are you facing issue only with the GoogleApps connector and other connectors for user import(if any) are importing users with correct accent? 

Rho
New Contributor III
New Contributor III

Hi,

I used this earlier today and it worked

^[a-zA-ZäöåÄÖÅ]+$

Test it and see if its helpful.

nimitdave
Saviynt Employee
Saviynt Employee

@Rho , thanks for the expression. But this will be evaluated when creating/updating user from UI. Correct?

Rho
New Contributor III
New Contributor III

@nimitdave we're using Azure AD connector, and the expression is in our lifecycle global configuration. 

Its worked both for UI & Import. Could it be that each connector has its own expression?