Show TOC

Configuring Users and SSO for SDICLocate this document in the navigation structure

Context

To be able to establish connection between the server on which the SDIC is located and the server(s) on which the SLD and the NWDI are located, you must establish a secured Single Sign-On (SSO) connection between the two systems. Once the user is authenticated on the SDIC server, an authentication ticket is generated and is used for further authentication with any of the targeted servers. Therefore you have to establish a trust relationship between the AS Java running the SDIC service and the AS Java running the NWDI

Procedure

  1. Configure an SSO trust relationship between the NWDI and SDIC servers. To do that open the SAP NetWeaver Administrator tool.
  2. Choose Start of the navigation path Operations Next navigation step System Next navigation step Application Manager End of the navigation path. In the page that appears find and select the functionality NWDI using CMS .
  3. In the Configuration Tasks tab page, select the task SSO Configuration .
  4. Choose Start of the navigation path Actions Next navigation step Execute via Configuration Wizard End of the navigation path.
  5. A dialog appears in which you have to fill in the required configuration details. Follow the steps of the wizard to configure the SSO.

    Select the SDIC checkbox Is a SDIC server used for this DI landscape? during the script execution.

    Note

    If your SIDE is using multiple tracks or development configurations on different servers, you have to execute the script for each track.

  6. The users logging into SIDE must also have the relevant permissions on the NWDI server to use its services for operations such as checkout (from DTR), activate (from CBS) and release (from CMS). You should also verify that these users have the required actions assigned to them for each of the NWDI servers. For more information, see Authorizations .
  7. If you are using the LDAP server for user management, ensure that the SDIC user is available on the LDAP server.