Skip to main content
Newcomer
Jan 17, 2023 8:09 AM UTC
Solved

Issue with bulk native user creation using internal authentication.

When creating a loadable xml format for bulk user creation using internal authentication, we face issue while signing in using the created users (the password encryption and decryption might have caused it)
Is there any way out to solve this?
For eg. : We created a user TestOS with password as Welcome1 using xml, but when this user tries to log in using the same credential, the user faces sign-in issues.

Jan 17, 2023 10:43 PM UTC

You have two choices:
(1) Do not include the <encryptedPassword> line in the XML file, in which case all new users will have the default password of 'OneStream'.
(2) Manually change the password of TestOS to 'Welcome1' in the OneStream client. Extract the security xml and use TestOS's encrypted password string for your new users. It will be the encrypted version of 'Welcome1'.

Users will be required to create a new password when they login for the first time in either case.

3 replies

Member
Jan 17, 2023 4:39 PM UTC

I don't think you can create users using XML unless you somehow know what encryption OS is using to generate that password. Your best bet is to do that using a rule

Jan 17, 2023 10:43 PM UTC

You have two choices:
(1) Do not include the <encryptedPassword> line in the XML file, in which case all new users will have the default password of 'OneStream'.
(2) Manually change the password of TestOS to 'Welcome1' in the OneStream client. Extract the security xml and use TestOS's encrypted password string for your new users. It will be the encrypted version of 'Welcome1'.

Users will be required to create a new password when they login for the first time in either case.

ishaanandAuthor
Newcomer
Jan 18, 2023 6:15 AM UTC

Hi,
We tried with the first step by removing the line and it worked. The default password "OneStream" works while logging in.
Thank you so much for the extended support.