How to avoid offending usernames?

[Community_User]

Originally posted on October 30 2019 at 12:24 UTC

Has anyone found a way to avoid offending usernames without having to perform the following:
- Create offending usernames into the system so these are not taken anymore.
- Have the username generation rule in the backend as there are other rules that I would like to keep visible in the GUI.

[Community_User · Accepted solution]

Originally posted on November 11 2019 at 09:04 UTC

For now, you can use the above itself. A new capability for applying pre-processing is planned for 5.5, which will make this easier.

[Community_User]

Originally posted on April 14 2020 at 13:41 UTC

Can we get some more information on preprocessing and what is the config?

[Community_User]

Originally posted on April 15 2020 at 03:11 UTC

Hi Pallavi,

Below is the link for document.

https://saviynt.freshdesk.com/support/solutions/articles/43000556603-user-import-preprocessor

Thanks

Ajay

[Community_User]

Originally posted on May 27 2020 at 16:09 UTC

Is the idea with offending names to create an additionalTable with all the offending names, and then check the username in the newuserdata against that set? How big can we make additionalTables?

Alternatively, can we create a custom table through the interface to manage those names or a word list, then reference that in a preprocessquery?

--Jim