User Provisioning Document

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 5

User Provisioning:

Requirement: When a new user creation is required, we need to send a mail to user with
cc to ERP_SAP_SECURITY group mail and ask to fill the Wiley access request form with Model id
and business justification details.
Once we get the RITM Request, we need check the requested user ID present in EP1 or
BP1 system if the ID is not present we need to follow below steps.
 Based on Wiley Access request form provided by user we need to assign the
required job role’s in EQ1 system initially.
 Create the Sample User ID in EQ1 as T_UserID and First name and last name last
name.

Also deactivate the password and user group should be TEST as below.
Now Assign the Required Role’s. and Save.

Now Log onto GQ1 system, goto SPROReference IMGGRCAccess ControlSync


Jobs
Repository Obj Job and select the required system and run.

Now goto NWBCAccess ManagementRun User Level Simulation as below and


execute for the required roles.
Attach the SoD Report and send an email to role owner approval for appropriate role
owners.
If there is no SoD Violation please ignore joe Carpin approval.
If there is an SoD Violation, we need to get the Compliance approval form Joe Carpin.

Once we revceived role owner approval and SoD approval if any, then we need to create
an User ID in EP1 system as below.
First name and last name of first letter should be Caps.Also email ID should be
Maintained(CAPS ONLY) as SKOTLA@WILEY.COM.

For All the user password should be Deactivated and user group should be Business
user.
Above SNC needs to be maintained as p:CN=USERID@WILEY.com

Then Maintain the parameters tab as same as like the model id parameters.

Then goto Roles, assign the appropriate roles which approved by role owner and save.

Once done with user creation please send an email to user and request user to check
the access whether they able to access or not. Also please update the ticket and close
the ticket once user confirms.

You might also like