HOW TO SAP

GRC 5.3 Create Password Self Service

December 09, 2017 grc 5.3, password self service,

GRC 5.3 - Create Password Self Service with Challenge Response with the following steps:

GRC > CUP > Configuration > Self Service >
Authentication Source : Challenge Response
Select Service to Disable Verification: None
Scroll down > Create > Now add your questions > Save
Repeat step 4 for other questions
Change >
Number of questions End User has to register : 2
Number of unsuccesful attempts after which user is locked: 3
The above value is up to your to define
To make PSS link visible at main AE page > CUP > Configuration > Request form Customization
Check password self service > Change > Visible : Yes > Save
Its visible now
CUP > Configuration > Connectors > Look for existing connectors > Change PSS to Enable
If you failed to perform step 10, you will not see the child system when requesting for password reset
CUP > Configuration > Workflow > CUA SYSTEM > Create / Change to ensure you identify child - parent relationship of your CUA systems.

GRC 5.3: Set Valid To Date to 12/31/9999 for new user

December 07, 2017 grc 5.3, valid to date,

GRC request result in valid to date of 12/31/9999 this can be done by:
CUP > Request form customization > User Valid To > Set Default Value = *

SAP SECURITY AUTHORIZATION: S_TABU_DIS has no 01 Activity

December 05, 2017 object, s_TABU_DIS,

Given the high criticality and increasing complexity related to table access –
SAP® has introduced a new authorization object for a more refined
table access control.

The authorization object S_TABU_NAM was introduced last year.
This authorization object consists of two fields ACTVT (Activity)
and TABNAME (name of table or view).
This concept is valid for generic table access through transactions like SE16,
SE16N, SE17, SM30, SM31, SM34 as well as generic function modules
(e.g. RFC_READ_TABLE)

The authority-check was integrated in the function module
VIEW_AUTHORITY_CHECK as per Release 7x with corresponding
Support Packages (Please refer to OSS Notes 141950 and 1434284
for more details).

To make sure the new object is downwards compatible with the previous
checks on S_TABU_DIS and S_TABU_CLI where applicable;
the check will only be performed if the check on S_TABU_DIS was not successful. Continue Reading