Show TOC

Defining Application AuthenticationLocate this document in the navigation structure

Assign a security profile to the selected application. The security profile defines parameters that control how the server authenticates the user during onboarding, and request-response interactions with the back end.

Prerequisites

In a production environment, configure security profiles for application authentication. In a development or test environment, you can use a security profile such as Default.

Context

Security profiles are made up of one or more authentication providers. These authentication providers can be shared across multiple security profiles, and can be modified in Management Cockpit. For more information about authentication providers, see Authentication in SAP Mobile Platform.

You can stack multiple providers to take advantage of features in the order you chose; the Control Flag must be set for each enabled security provider in the stack.

Procedure

  1. In Management Cockpit, select Start of the navigation path Applications Next navigation step Authentication End of the navigation path.
  2. Click Existing Profile.
    Note You can also create a new profile. In Management Cockpit, select Start of the navigation path Security Profiles Next navigation step New End of the navigation path.
  3. Select a security profile name.
    The name appears under Security Profile, and the providers that are associated with the security profile appear under Authentication Providers.
    Note (Applies only to Mobile BI) The administrator can choose a security profile from the list of security profiles and that profile becomes the default profile for the current Mobile BI application. The Mobile BI applications are allowed to send an X-SMP-SC header during the registration request, which can override the security configuration assigned to the Mobile BI application in Management Cockpit. After registration, all requests use the same security configuration that was used while creating the application connection ID. Normal data requests with an accompanying application connection ID retrieve the security profile used during the application connection ID registration and use it for authentication.
  4. (Optional) Enable Check Impersonation.
    Note In token-based authentication, whether to allow authentication to succeed when the user name presented cannot be matched against any of the user names validated in the login modules. By default the property is enabled, which prevents the user authentication from succeeding in this scenario.
  5. Under Authentication Providers, you can select a security profile to view its settings. To change its settings, select Start of the navigation path Settings Next navigation step Security Profiles End of the navigation path.