This document contains instructions on how to configure the Netweaver UME and SAP Sourcing to create users in the UME and sourcing without the normal initial password reset. By default any user created in the UME will have a pre-expired password. This means the initial login will work but has to be reset on the first login. For temporary accounts where a predetermined password needs to be used, this is inconvenient. This procedure will outline how to create users with predetermined passwords and keep those passwords for the duration of a test event.
NOTE: This is not a recommended procedure for normal productive use. It is intended for use in test /QA systems and is provided as a convenience.
Step 1
Login to Netweaver NWA as Administrator or similar account with admin access.
Select Operation Management --> Identity Management --> Configuration --> Modify Configuration --> Security Policy. Uncheck the “Allow Users to Change Their Own Passwords” checkbox. Update the Password Validity period at least the amount of days the testing event is going to occur (so if anyone’s password was going to expire during the test period it would not) save all changes.
Create users in UME using the import capability. The following is an example import text file for users testimp1, testimp2 and testimp3.
[User]
uid=testimp1
last_name=Import1
first_name=Test
password=Initial1
email_address=gary.boutin@sap.com
accessibility=0
role=admin;
[User]
uid=testimp2
last_name=Import2
first_name=Test
password=Initial1
email_address=gary.boutin@sap.com
accessibility=0
role=admin;
[User]
uid=testimp3
last_name=Import3
first_name=Test
password=Initial1
email_address=gary.boutin@sap.com
accessibility=0
role=admin;
Results of successful creation of 3 users in UME.
Prepare a contact import file for SAP Sourcing that will match the users created in UME.
Fields to consider:
VENDOR_EXTERNAL_ID – The Vendor that this user will belong to
NAME – To match the uid in UME
DIRECTORY- The external ID of the sellside directory
FIRST_NAME - To match whats in UME
LAST_NAME -To match whats in UME
EMAIL – (whatever)
INACTIVE - FALSE
CAN_LOGIN - TRUE
CREATE_DIR_ACCOUNT – FALSE
GENERATE_NEW_PWD – FALSE
SEND_NOTIFICATION – (optional)
BUSI-00696,,,,testimp1, ,someone.ume.sellside.dir,,,Test ,Import1,,,,,,,,,,,,,,,gary.boutin@sap.com,,,,,,,,,,,FALSE,TRUE,,,, , ,TRUE,,,,,
BUSI-00696,,,,testimp2, ,someone.ume.sellside.dir,,,Test ,Import2,,,,,,,,,,,,,,,gary.boutin@sap.com,,,,,,,,,,,FALSE,TRUE,,,, , ,TRUE,,,,,
BUSI-00696,,,,testimp3, ,someone.ume.sellside.dir,,,Test ,Import3,,,,,,,,,,,,,,,gary.boutin@sap.com,,,,,,,,,,,FALSE,TRUE,,,, , ,TRUE,,,,,
After testing is complete, use the same import file(s) to inactivate these users. This can be done either in Sourcing or UME (preferably both).
Undo the changes made to the UME configuration in step 1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
16 | |
5 | |
2 | |
1 | |
1 | |
1 | |
1 |