Enabling Single Sign-on for DOE-C Packages

Enable single sign-on (SSO) over secure paths for Data Orchestration Engine Connector (DOE-C) packages.

1. Preparing Your SAP Environment for Single Sign-on
   Verify that the SAP® enterprise information system (EIS) is configured correctly to accept SSO connections from Unwired Server.
2. Configuring X.509 Certificates for SAP Single Sign-on
   Import, export, and generate the X.509 certificates that secure communication paths between Unwired Server and the SAP enterprise information system (EIS), and for client authentication, including single sign-on (SSO) with X.509 or SSO2 tokens.
3. Deploying and Configuring DOE-C Packages
   Deploy the ESDMA (DOE-C package) to an Unwired Server domain using the DOE-C command line utility (CLU).
4. Creating Security Profiles to Enable Mutual Authentication for SAP
   Create security profiles and associate them with X.509 server certificates that can be used to establish secure connections between a client, Unwired Server, and the SAP EIS.
5. Enabling the HTTPS Port and Assigning the SUPServer Security profile
   Enable an HTTPS port for secure communication between Unwired Server and the SAP EIS.
6. Enabling the DOE-C Connection and Assigning the TechnicalUser Security profile
   Configure the SAP Data Orchestration Engine Connector (DOE-C) connection pool between Unwired Server and the SAP EIS. This is the port on which Unwired Server communicates with the DOE, including forwarding subscriptions and allowing client operations to flow through to the DOE.
7. Security Configurations That Implement Single Sign-on Authentication
   Use the CertificateAuthenticationLoginModule authentication module to implement X.509 authentication or HttpAuthenticationLoginModule to implement SSO2.
8. Seeding Messaging Devices With Unwired Server
   If you are not using Afaria, you can install the client application then connect to corporate LAN using Wifi or any other method of your choosing in order to seed devices with required files.