Several single-sign on access policies are available for the SAP environment. This enables users to be authenticated using a SAP logon ticket (SS02 Ticket) or an X.509 certificate.
Both replication- and message-based mobile clients can use SSO with:
- SAP data source support –
- SAP Data Orchestration Engine Connector (DOE-C) connections
- SAP Java Connector (JCo) connections
- SAP BAPIs exposed as Web services – both HTTP and HTTPS endpoints are supported
For information about developing mobile business objects for SSO, see the topic Implementing SSO for SAP in Unwired WorkSpace online help.
- Single sign-on credential support –
- X.509 certificates – at runtime, the mobile client selects the certificate signed by a trusted CA, which is authenticated by the SAP EIS.
- SAP single sign-on (SSO2) tokens – at runtime, the client enters a user name/password combination that maps to a user name/password in the SAP EIS. A token is obtained from the configured SAP server using
the client supplied user name/password and is forwarded to other SAP servers configured in the endpoints to authenticate
the client, instead of using client supplied user name/password credentials.
- Client support –
- Windows Mobile, iOS, and BlackBerry message-based clients
- Prebuilt applications, such as the Sybase Mobile Sales for SAP CRM
- Windows Mobile, iOS, and BlackBerry replication-based clients
- Workflow clients