SUIM's Authorizations Assistant enables you to resolve authorization errors such as "access denied", which are complicated and lengthy in the standard SAP case. AA simplifies traditional unit testing by automatically creating delta roles based on failed authorization checks. Based on a green list/red list, delta roles are automatically assigned to testers so they can continue testing without interruption.
With one click, the end-user sends all necessary information to the system when an access is denied. AA automatically enhances the role if predefined security criteria are met. If not, AA proposes a simple workflow where an Administrator decides whether or not to grant the user a role enhancement. For new authorization concepts, if authorizations are not transfered equivalently, AA automatically checks whether the user would have had the equivalent rights under the old concept and grants them (depending on predefined criteria) automatically. AA offers massive time savings when testing new systems, during system upgrades or when introducing new authorizations concepts.
Efficiency
Flexibility
Simplicity
Authorizations related entitites
Identity related entitites
Integration with 3rd parties products
Integration in other SUIM products
How to test a new authorizations concept
The Authorization Error Cockpit gives you a powerful insight into the areas where many authorizations were requested
?
List of red-listed authorizations can be defined to signal if an authorization is missing and if it should be assigned or ignored.
Risks can be defined (for example Critical Authorizations, Critical actions or SOD violations). A risk violation can prevent automatic role enhancement
An intuitive customizing workspace for configuring AA is included
The content of your authorization templates can be optimized based on your role content
?
When you go live with a new role concept, a reference user can be used to assign authorizations from the old concept as needed. This ensures a smooth go-live, as no authorization errors occur
If permissions are missing, AA automatically creates a role, following naming conventions and taking into account red lists
?
Automatic assignments mean that testing is never hindered by authorization errors
?
In case of authorization problems, AA can scan the authorizations in a reference concept automatically or on request
If the user had the missing authorizations in the reference concept and this authorization is not in red-listed, AA sends an event
In response to this event and depending on the configuration from the AA, the addition of this object is done automatically or via workflow
?