Binding a Mobile Client
To use mobile services, you must represent your mobile app in OpenShift using a Mobile Client, and that Mobile Client must be associated with the mobile service. This association is called binding and once it’s done, your mobile app can use that service immediately.
|The association between a Mobile Client and Identity Management Service uses the Service Broker bind feature.|
To associate a Mobile Client with a mobile service:
Navigate to the Overview of your OpenShift project.
Click on the Mobile Client and navigate to Mobile Client view.
Your mobile app will be represented by two items in OpenShift, an item in the Mobile Clients list and an item in the Provisioned Services list. Make sure to click on the item in the Mobile Clients list.
Navigate to Mobile Services tab.
Click Create Binding and follow the Create Binding wizard to associate the Mobile Client with the Identity Management Service.
Fill out the binding parameters required by the Identity Management Service.
Choose the Keycloak client type. The default is
publicwhich allows the client to request tokens while type
bearershould be used to bind to services that only need to verify tokens.
publicclient type should be used to bind to Mobile Clients because they only need to request tokens, but not verify them. When binding to other services you should use client type
bearerunless they also need to authenticate.
The Identity Management service will now be expandable, details about the service can be viewed.