About Configuring Security and Authentication for Siebel Reports

Authentication between the Siebel application and Oracle Publisher Server performs the following:

1. Checks that a user exists in the directory as follows:

   • For LDAP, checks for a user in the directory.

   • For Siebel Security, checks by way of the endpoint that a user exists in the Siebel application.

   • For Oracle Publisher Security, there is no user directory check. The generic authentication credentials are checked against a user defined in Oracle Publisher.

   • For Oracle Publisher Security, responsibilities are not checked, instead the same generic user account is used for the connection to Oracle Publisher Server.

     Note: For more information on Oracle Publisher Security, see Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher or Administering Oracle Analytics Publisher in Oracle Analytics Server.

2. Checks that a user has certain roles depending on what action they are taking:

   • For LDAP, groups are created that relate to Oracle Publisher roles. Users in the LDAP directory have these certain groups assigned to them. Oracle Publisher authentication to LDAP directory checks for a user if they have a certain group.

   • For Siebel Security, each user has certain XMLP responsibilities. Oracle Publisher authentication to the Siebel application, by way of an endpoint inbound Web service call, checks that a user has the correct responsibilities that relate to the Oracle Publisher roles.

3. Checks Siebel XMLP responsibilities that control the Siebel user interface for Reports menu restrictions (for example, XMLP_SCHEDULER responsibility for the scheduling option).