Managing Registrations

Manage multiple native and hybrid application registrations from a single location. Registered applications are associated with a user, an anonymous user, or nosec_identity on one or more devices. When the user accesses the application from a device the application is registered. View information for all application registrations, or retrieve a filtered subset of registrations. From the list of registrations, you can drill down to see application and user details. For hybrid applications, if the developer has implemented Logger code in the application, you can drill down to upload and view client logs. You can also delete registrations.

1. From Management Cockpit, select Registrations on the Home screen to view application connections. Alternatively, in the Applications tab, click the Registrations tab.
   You see information for as many as 200 registered applications.

   Field	Value
   Registration ID	System-generated application registration ID.
   Application ID	Unique identifier for the application, in reverse domain notation. This is the application or bundled identifier that the application developer assigns or generates during application development. The administrator uses the Application ID to register the application to SAP Mobile Platform Server, and the client application code uses the Application ID while sending requests to the server.
   Device Type	The parameter value, such as Android and iPhone, sent by the device during registration/onboarding. "Unknown" indicates the device type cannot be detected.
   User Name	Name of a person using the application registration. If the application is configured to "Allow Anonymous Access", the user name "anonymous" is used for a successful registration, and can indicate: The user has not provided the credentials. The user has provided the wrong credentials. The URL is prefixed with /public/. If the security profile is "No Authentication Challenge", the user name "nosec_identity" is used for a successful registration.
   Registration Time	The date, time, and time zone the application was registered, in the format MMM DD YYYY HH:MM:SS TZ.
   Client Log	If client logging is enabled for the application and data is available, click to upload the client log to the server. You can specify the level of verbosity. Note: Client logs are available only for hybrid applications.

2. (Optional) Under Search Criteria, select filtering options to display a subset of application registrations:
   1. Under Application, select the Application ID or All to narrow the scope of applications.
   2. Under Time Frame, use the date picker to identify a specific date and time range.
   3. Under User, type a specific user name to search only for that name.
   4. Click Search.
      Registrations that meet your search criteria appear under Registrations.
3. (Optional) Use filtering and sorting options to display a subset of the registration results.
   • In Filter By, select Registration ID, Application ID, Device Type, or User Name, and enter a name to search for a specific entry.
   • Use column sorting and filtering to show only records that meet your criteria.
4. (Optional) View details:
   • Select an Application ID URL to view more details about a specific application.
   • Select a User Name URL to view more details about a specific user.

• Deleting a Registration
  Delete an individual registration, which includes Application ID, Device Type, and User Name. This is useful for deleting orphaned registrations, which can occur when a user is no longer using an application on a device, or has obtained a new mobile device, which requires its own registration. It can also be useful for clearing a registration while troubleshooting configuration issues. Once the registration is deleted, the user will not be able to use the application on the device unless they reregister the application.
• Viewing Client Logs
  (Applies only to hybrid) Download and view a client log associated with the selected application registration. The developer must have implemented Logger code in the application code, and the application must be registered and collecting data. Client requests to upload a log file are authenticated based on the application security profile. The log content varies by device type and operating system.
• Client Logs
  (Applies only to hybrid) If client logging has been enabled for a hybrid application and log data is available, you can view the client long for the selected application registration.