Propagating a Client's Credentials to the Back-end Data Source

Use client credentials to establish enterprise information system (EIS) connections on the client's behalf for all data source types.

1. During development of the mobile business object MBO/operation, from the data source definition page (available either in the Creation wizard or from the Properties view), in the Runtime Data Source Credential section (or HTTP Basic Authentication section for a Web Service MBO), enter the client credentials in the User name and Password fields. The runtime data source credential values (user name and password) that Unwired WorkSpace uses for refresh or preview operations is taken in this order:
   1. Any literal value entered in the User name and Password fields.
   2. User-defined personalization keys that have non-empty default values.
   3. User name and password property values contained in the connection profile.
2. During deployment of the package that contains such MBOs, map the design-time connection profiles to the existing or new server connections, but be aware that the username and password portions for the selected server connection is replaced by the username and password propagated from the device application.
   Note:

   • Do not set client credentials using the Runtime Data Source Credential option for MBO's that belong to a cache group that uses a Scheduled policy, since this is unsupported.
   • In general, a MBO operation that uses data source credential settings as connection properties cannot have these settings mapped to an enterprise information system (EIS) during deployment. Instead, they maintain their original settings, which you can map after deployment using Sybase Control Center (SCC).
   • When you create a new security configuration that includes the SAPSSOTokenLoginModule, and deploy it to a new domain, if the mobile workflow application uses the MBOs associated with the new security configuration, you must specify an Unwired Server domain that corresponds to the domain using the security configuration. See the Sybase Unwired Platform Security guide for more information about security configurations

• Configuring a Workflow Application to Use SSO2 Tokens
  Configure a Credential Request starting point from which a workflow application user can pass a user name and password to gain access to the MBO and related resources.
• Configuring the Workflow Application to Use a Static SSO2 Token
  When using static credentials, the workflow application does not prompt the user for credentials, instead it passes the credentials to Unwired Server automatically and displays the workflow application's start screen.