Free cookie consent management tool by TermsFeed Mobile Authentication Requirements
Mobile Authentication Requirements


If you have special network configurations and are using Appian Mobile, it is important to understand how the mobile application authenticates with the Appian server, so that your users are able to seamlessly use the application. This page explains how mobile authentication works, the network requirements, and the supported methods for restricting access to the Appian server.

How Mobile Authentication Works

To understand Appian Mobile's network requirements, it helps to understand how the client and server communicate during mobile authentication.

mobile authentication sequence diagram

  1. The mobile app requests a resource from the server.
  2. The server determines that the request is not authenticated.
  3. The server replies with a 401 status code and a JSON payload containing a context URL and token URL. Example:
       "contextUrl": "",
       "tokenUrl": ""
  4. The mobile app examines the response and determines two things:
    • The response has a 401 status code with contextUrl and tokenUrl keys and came from an Appian server.
    • The app needs to authenticate with the server.
  5. The app constructs a "login" URL that contains a number of important query parameters needed to set state on the server. It then prompts the user to sign in by opening the login URL in the user's web browser. Example:
  6. The user signs in using the web browser. If the web browser already has a session with the Appian server, it will be terminated prior to prompting the user to sign in.
  7. When the user successfully authenticates with the Appian server, the server redirects the web browser to a "callback" URL that uses the scheme provided by the login URL and contains a "token" value. Realizing that the scheme of the requested URL corresponds to the mobile app, the web browser forwards the callback URL to the app. Example:
  8. The app closes the web browser.
  9. The app makes a POST request to the "token" URL received in step 3. The body of the request contains the token returned by the web browser.
  10. The server uses the token to establish an authenticated session.
  11. The server returns a "bootstrap" response with information about the user and session cookies that allow the app to make subsequent requests without reauthenticating.

Network Requirements

Mobile app requires direct communication with the Appian server

In order for the authentication flow described above to complete successfully, the mobile app must be able to communicate directly with the Appian server.

Appian does not support any configuration in which Appian Mobile needs authentication cookies to reach the Appian server.

Requests and responses cannot be modified

If communication between the mobile app and server is routed through an intermediary, such as a load balancer or proxy, both the request and response must remain unmodified.

Appian does not support any configuration in which Appian Mobile receives HTTP responses from a server other than an Appian server.

Supported Methods for Restricting Network Access to the Appian Server

Appian Mobile supports two methods of restricting network access to the server: VPNs and Client Certificates.


Appian Mobile can connect to a VPN-protected server as long as the mobile device is connected to the VPN. Mobile devices can connect to a VPN at the operating system level or with a per-app VPN configured through MDM.

Client Certificates

The Appian server can be secured behind a network gateway that issues certificate challenges. Appian Mobile allows users to import a client certificate to be used whenever a certificate challenge is received. See Client Certificate Access for more information.

Mobile Authentication Requirements