GRC 5.3 - Valid to date is always the current date during submission of a new request

GRC 5.3 - Valid to date is always the current date during submission of a new request

November 30, 2017   current date, grc 5.3, valid to date,

1. GRC 5.3 provision user with validity period the same day user was created. SU01 screen as below:
   
2. In GRC you can see the following when request for a new account:
   
3. This was cause by following settings in GRC 5.3 in Configuration > Field Mapping > LDAP Mapping > Additional Fields > validToDate
   
4. Remove this entries and try again.

Continue Reading

HOW TO SAP - Perform system trace for missing authorization

HOW TO SAP - Perform system trace for missing authorization

November 29, 2017   authorization trace, st01, system trace,

How to perform system trace for authorization

1. Execute tcode ST01
2. Check Authorization Check (you may select more)
   
   
3. Click Trace On (Make sure to turn it off after you are done!)
   
   
4. Now ask user to perform their task.
5. *If there is more then one app server, go tcode SM51
6. *Then double click on the app server.
7. *Then repeat step 1 to 3
8. Remember - Once user completed the test, turn of all trace from ST01
9. Now, click Analysis
   
   
10. Filter the trace like below (select what you need)
11. For authorization issue, anything above RC=0 meaning there is missing authorization.
    

Continue Reading

VIRSA - HOW TO export mitigation control

VIRSA - HOW TO export mitigation control

November 28, 2017   export mitigation control, virsa,

1. SA38 or SE38 and execute  /VIRSA/ZVRAT_L03
2. Enter the following details:

3. Exported file looks like:
Continue Reading

SOD Scan using /n/virsa/zvrat

SOD Scan using /n/virsa/zvrat

November 26, 2017   sod scan, virsa,

1. Tcode /n/virsa/zvrat
2. Ok
   
   
3. Enter userid
   
4. Choose the system where user id was created
   
   
5. Then execute
6. If the system id was not found, you may add the system using those entries in SM59.
7. To add, execute /n/virsa/zvrat_s16
8. Select Comp Calibrator Configuration
   
   
9. Under Parameter 19, add in a new system
   
   
10. Save and try scan again

Continue Reading

GRC 5.3 SNC - Provision with upper case userid which cause SNC to fail

GRC 5.3 SNC - Provision with upper case userid which cause SNC to fail

November 25, 2017   cup, grc 5.3, lowercase, snc, su01, uppercase,

1. GRC 5.3 is able to provision SNC settings to SU01 but USERID appears in upper case format as below:
   
   
2. SNC is case sensitive, thus it will failed when user tried to login.
3. Because GRC 5.3 convert user id to UPPERCASE as below:
   
   
4. This can be resolved in two step.
5. Step 1: Configuration > Request Form Customization > SNC Name > 
   Default value > p:#!#userId#!#@DOMAIN.COM
   
   
6. Step 2: Configuration > Field Mapping > LDAP Mapping > Additional Fields > Add SAP_User_ID and then map it to the correct LDAP fields. In our case, its "mailNickname" because it is in lowercase.
   
7. GRC will then replace userId with the LDAP field "mainNickname" which is in lowercase
   
   
8. Once provision, SNC field in SU01 will be in this format p:zmolan@DOMAIN.COM

Continue Reading