An application connection can be activated from the device by either providing valid credentials, or an activation code for a pre-registered application connection. The credentials-based approach, referred to from this point on as automatic registration, relies on application connection template properties (application ID, security configuration, automatic registration enabled). The activation-based approach, referred to from this point as manual registration, relies on matching user name and activation code sent from the device to an existing application connection registered for the user.
Application template are used for automatic activation. Therefore, when setting up the application template for automatic registration, be sure to set up the security configuration, domain, the application ID, and automatic registration enabled properties in application settings. Those are used for automatic application registration.
When a client application connects to the server with its application ID and credentials, and requests automatic registration, the application ID is used to look up a matching template. If that template allows automatic registration (the Automatic Registration Enabled property is set to true),the security configuration in the template is used to validate the credentials. Upon successful validation of those credentials, the user identity is registered in the Unwired Server. The client application may also include the security configuration as part of the username (user@securityconfiguration) and in that case, the security configuration (in addition to application ID) is used to look up a matching template. If no or multiple templates are detected, the registration request fails.
| Device Client Type | Automatic Registration | Manual Registration |
|---|---|---|
| Workflow messaging | X | X |
| Native messaging | X | |
| Online Data Proxy | X | X |