Profile securities
XML name |
core:ProfileSecurity |
Class name |
de.lobster.scm.dw.profile.ProfileSecurity |
Rights |
Administration/System/Profile Security |
Access to profiles in Lobster_data via portals and input forms in Lobster Data Platform / Orchestration (e.g. via the action Call profile or Validate element and call profile) can be controlled by 'Profile securities' based on the names of the profiles.
►IMPORTANT◄ Without the creation of profile securities, _data profiles are basically not accessible from Lobster Data Platform / Orchestration.
A 'Profile security' can either allow or forbid access to certain profiles, depending on whether the Accessible (2) checkmark is set or not.
The Profile name pattern (1) determines to which profiles the control (access or no access) should be applied. The exact profile name (e.g. 'Profil A') or a regular expression enclosed in slashes (e.g. '/^SCM_/') can be specified here.
The Description (3) is optional.
When creating interactive profile securities, the company of the session is automatically entered as the owner of the profile security. Access to or applicability of profile securities depends on the owner and possibly also on permissions and inheritances. The input for the 'owner' can also be deleted. Then access to the profile security in question depends only on the role used and not on the company context.
Interpretation of competing profile securities
In some circumstances, matching the patterns specified in profile securities with a particular profile name returns multiple matches. These may even contradict each other in their 'polarity' (access allowed or forbidden).
The system evaluates competing and possibly contradictory data for access to a profile according to the following rules:
The 'matching' profile securities are divided into the categories 'exact' (pattern=profile name) and 'fuzzy' (regular expression).
A count is made whether there is a majority for the polarity 'allowed' or 'forbidden' for each category.
If there is a majority decision for the exact matches, it determines the access to the profile.
If there are no exact matches or no majority among them, the majority of fuzzy matches decides whether the profile will be accessed.
If both categories are either empty or tied, no access to the profile will be granted.