SAP Authorizations Reset passwords using self service - NW Admin

Direkt zum Seiteninhalt
Reset passwords using self service
Security in development systems
When were which changes made to a role (PFCG)? In the PFCG, click on Utilities > View Changes in the menu at the top to view the change documents. You will see a detailed list of which user made which change to which object and when.

Another important factor that should be considered in an authorization concept is to use a uniform naming convention because, on the one hand, many things cannot be changed after the initial naming and, on the other hand, this ensures searchability in the SAP system. In addition, the preset authorization roles of the SAP system should never be overwritten or deleted, but only copies of them should be created, which can then be adapted as desired.
SAP Security Automation
Communication users are also intended for use by people who log on to the SAP system from outside via RFC call. Therefore, dialogue is not possible. If the password is set by the administrator, it will be assigned Initial status. However, an RFC call does not prompt the user to change the password. It therefore often retains this status, even if the user has the possibility to change the password by calling a function block (then: Status Productive). The password rules apply to this type of user. However, this is often not noticed in practice, as password rules for initial passwords are less used.

A note box in which data of all kinds can be quickly filed and retrieved. This is what Scribble Papers promises. At first, the program looks very spartan. But once a small structure is in place, you realise the great flexibility of this little helper.


Single Role: Enables the automatic generation of an authorization profile. The role contains the authorization data and the logon menu for the user.

If you get into the situation that authorizations are required that were not considered in the role concept, "Shortcut for SAP systems" allows you to assign the complete authorization for the respective authorization object.

If, before mixing, permissions were already in the Maintenance status Standard (this applies to both Active and Inactive) or Inactive Standard, the underlying programme compares the values and the associated Maintenance Status of all eligibility fields and checks to what extent new suggestion values are present in the transaction SU24 and whether new permission fields must be added.

Now open the Menu tab and follow the path: Tools > Customising Permissions > Add > Insert Customising Activities.
NW BASIS
Zurück zum Seiteninhalt