Automatic
connection registration is the process by which a user and application ID is paired to an
connection by using the authentication identity. It is considered automatic, because the
administrator does not need to manually create this pairing by selecting the in-bound
connection and registering it in
SAP Control Center.
For automatic connection registration, administrators must create a
connection template and use it with the application definition. The combination
application ID, domain, and security property values must be unique.
Note: For messaging clients, automatic registration will not work if the
user name contain i18n characters.
A connection that is
registered allows the application to become activated (that is, allowing it to consume
data and services of SAP Mobile Platform). The activation process
for automatic connection registration follows this sequence:
- Login – the user sends credentials via the application the security provider.
- Authentication – the security provider delivers the authentication result to
SAP Mobile Server.
- Connection registration – the user identity is extracted (which may include a security context as in
user1@SecurityConfiguration1) and paired with a device ID and one or more
applications IDs.
- Connection activation – the registration information identifies required packages, customizations,
and connections on SAP Mobile Server. If the
Automatic Registration Enabled property for the
connection is set to True, then the template
automatically creates a default connection for the application on
SAP Mobile Server.
- Application activation – the device synchronizes settings from the server, and returns device
information back to the server. For example, the registered application
connection is updated with a phone number, IMSI, device type, and
perhaps native push configuration information that is used to deliver
notifications via device-specific infrastructures for Apple, BlackBerry,
or Android.