Siebel Application Interface Profile Parameters

The Siebel Application Interface profile contains parameters that control interactions between the Siebel Web Engine and the Siebel Application Interface for all Siebel Business Applications deploying the Siebel Web Client.

The Siebel Application Interface profile includes a Basic Information section for defining Authentication, Logging, and REST Inbound Defaults, an Other Information section for defining SWE, and an Applications section for defining Basic Information, Mobile, and Enhanced Authentication for individual Siebel Business Applications. Each parameter value in the Basic Information section is used by all individual applications, unless you override the parameter’s value (for a specific application) with an entry in the Applications section.

You can edit the parameters in the Siebel Application Interface profile using the Siebel Management Console. For information on using the Siebel Management Console to configure application interface profile parameters, see Siebel Installation Guide.

In a given Siebel Application Interface profile, some parameters might not appear by default. For more detailed information on application interface profile parameters, see:

Note: Before you create and configure a Siebel Application Interface profile, make sure that you have already deployed the Siebel Server. After you have done this, the Object Manager and Application settings in Siebel Application Interface profile configuration are populated with values you can choose from that reflect available components on the Siebel Server. After you deploy a Siebel Application Interface profile, the profile is in a read-write state. You can update the configuration settings and save the profile to propagate the updates to the deployed Siebel Application Interface.

Siebel CRM supports the following security profiles:

  • Application Interface profiles, which require a 1:1 mapping to security profiles (Database, LDAP, or Custom).

  • For object manager-based UI applications, either Basic or SSO authentication is supported on the defined security profile.

  • For object manager-based REST channels, Basic, SSO, or OAuth authentication is supported.

  • For non-object manager REST calls, authentication types are not controlled by the Application Interface profile so the Basic authentication type is used with the defined security profile. For example: srvrmgr, Gateway and Siebel Manager Console-specific (non-object manager) REST calls.

  • Components that are not part of the Application Interface can override the basic security profile and use a different security profile.