Mobile applications

Mobile applications are part of the group named Native Applications in the OpenID Connect documentation. They have very similar security properties compared to the Browser based applications but they are considered a bit easier to secure, because you often have stronger platform support for protecting data and isolation. For this flow you will get client id configured for the authorization_code flow. Classic web application that render content on the server could also use this flow.

This endpoint uses token endpoint, so there is communication between the client and the identity provider that does not go through the user’s browser.

  1. When the user tries to access the client application, client application makes a GET request to a authorize endpoint.

  2. As a result, user receives the login screen on our identity provider where he needs to enter his credentials.

  3. After successful verification of the credentials, user is redirected to the predefined client redirect URL and at this point client application is capture authorization code from the URL parameter.

  4. Authorization code cannot be used to call APIs. It is used to make a POST request to get an access token. This call does not go through the user’s browser. It is direct communication between client and identity provider.

  5. Response of the previous call will be JSON payload with the access token that can be used to call KS Connect API.

If the GET request in step 1 contains the scope offline_access, response in step 5 will besides the access token also include refresh token.


* this is example call without real client id

Because refresh token has much longer lifetime it can be used to obtain another access token with a POST call to the token endpoint.

POST connect/token
Content-Type: application/x-www-form-urlencoded
Authorization: Basic Y2xpZW50X2lkOmNsaWVudF9pZF9zZWNydGV0

* this is example call without real client id

App storePlay store