User Types
The AS Java is an application middleware component in your technical landscape. Therefore you can use it for communicating with various communication destinations and data sources.
During the AS Java installation, you create standard users to use for user access and communication purposes. Depending on the user purpose, you can apply different security policies to created users after the installation is complete. To facilitate this process the UME of the AS Java classifies users based on the user attribute Security Policy.
More information:
Creating a
Technical User.
Description of User Types (Security Policy Attribute)
User Type |
Description |
Default Users |
Used for regular generic users. Users of this type have the following characteristics: · Can log on to the AS Java by providing authentication credentials interactively or with SSO. · Normal password rules apply, for example the user’s password can expire or the password must be changed after initial logon. · Created by administrators, during self registration, or read from external UME data sources. The administrator and guest users are created automatically during installation. · UME maps (A) Dialog users from the AS ABAP data source to this type. Well known users of this type include: administrator and guest. |
Technical Users |
Used for system to system communication. Users of this type have the following characteristics: ● Can be used to log on to the AS Java. ● Password does not expire. ● Some created automatically (SAPJSF), some by the user administrator. ● UME maps (B) System users from the AS ABAP data source to this type. Well known users of this type include: SAPJSF and ADSuser.
Although SAPJSF is a technical user, you cannot log on to the AS Java with it for security reasons. More information:
|
Internal Service Users |
Used to perform internal operations, for example PCD ACL operations for a portal. ● Cannot be used to log on. ● Usually do not have passwords. ● Normally created automatically. ● Users exist only in the Java database and do not map to other data sources. ● Type cannot be changed. Well known standard users of this type include: pcd_service, config_fwk_service, and ume_service. |
Unknown Users |
This type cannot be created from the UME and exists only as mapped from an AS ABAP data source. ● UME maps to this type AS ABAP users of type (C) Communication, (S) Service, and (L) Reference. ● Unknown users of this type have the same characteristics as Default users. ○ Can be used to log on. ○ Normal password rules apply. |
