|Note:||This tab is only available to users with account holder credentials.|
In a Nutshell
It is in the Account tab where you can view account information.
It is an Account to which Companies and Users are assigned, and to which subscription billing information is sent.
A Closer Look
When you navigate to the Account tab, you will see the following information:
|ID||The unique ID of the account. This value is automatically generated by the application.|
|Name||The name associated with the account.|
|The email address associated with the account.|
|Cluster||The location of the server cluster associated with the account.|
|Login Enabled||Yes or No. When yes, the user associated with the account will be able to login.|
|Password Expiry Date||The expiration date of the account password.|
|Password Status||The current status of the account password.|
|Roles||The role assigned to the account. Examples include:
|Tenant ID||The SAP Tenant id associated with the account.|
|Type||The type of the account. Examples include: “Productive” or “Customer Test Tenant”.|
|Number of Licenses||The number of licenses purchased for the associated account.|
|Valid From||The date from which the licenses for the associated account are valid from.
Note: In the new license model only one contract start date is supported. In case of legacy contracts with different start dates we display the earliest start date only.
|Valid To||The date until which the liceneses associated with the account are valid.
Note:In the new license model only one contract end date is supported. In case of legacy contracts with different valid to dates we display the latest valid to date only.
|Ignore Coresystems Subscriptions||True or false. The flag to define if the associated account is managed by legacy model based on different types of subscriptions or if the new access model is enabled that ignores subscriptions and is based on activating users and assigned the corresponding user group per company.|
|Clients (legacy API)||If applicable, the using the legacy API which are allowed to access the specific account. This list is exclusive for all clients using the legacy API.
Note: This setting does not have any effect on updated clients using the recommended OAuth2 API.
|Clients (OAuth2 API)||If applicable, the allowed IP ranges of client ids. This list is exclusive which means access is only possible for the clients and IP ranges defined here.
Note: In case only one client application is defined here, the access is disabled for all other clients. See below information about available client id.
|Minimum Client Version||If applicable, minimum versions required for different clients. In case a specific client application is not defined here access is allowed for any client application version. This can be used to ensure that users are using a version that contains a specific functionality that is required for the business.
See the section below for information about available client ID.
|Default SAML Configuration||If applicable, select the default SAML configuration for the associated account. For more information on SAML, please refer to the following topic on Federated Authentication.|
|Email Login Supported||When
ATTENTION: To be able to manage the account assign at least one user to the.
|Legacy Password Hash Supported||
|Legacy Authentication Log-In Supported||
|Client Authentication Throttling||
|Strict Data Access||
ATTENTION: this includes SAP and Coresystems Support and therefore can slow down the support process.
|Wrong Password Attempts||The number of wrong password attempts that were entered.|
Available Client IDs
A minimum version can be configured for the following clients:
|App Name||Short Description||Client Id|
|Analytics & Reporting||AR||reporting|
|Master Data Management||MDM||master-data-management|
|Mobile Field Service App - Android||Android||android|
|Mobile Field Service App - iOS||iOS||ios|
|Mobile Field Service App - Windows||Windows||windows|
|Report Designer (JasperSoft Plugin)||RD||reportdesigner|
Client ID can be entered into the client ID field, after which an
IP Address or
minimum version can be set for it in the field beside it (example: