Skip to main content

Add native or mobile application

A native or mobile application runs directly on a user's device — iOS and Android apps are common examples. A mobile shopping app or a desktop productivity tool are typical use cases.

Because the app binary can be inspected, native apps cannot safely store a client secret. SecureAuth registers them without one and uses Proof Key for Code Exchange (PKCE) to keep the sign-in flow secure.

Before you begin​

You'll need:

  • Access to your workspace in SecureAuth
  • The redirect URI for your application (often a custom URL scheme like myapp://callback)
  • Access to your mobile or desktop application code

Add the application​

  1. In your workspace, select Applications > Clients > Create client.

  2. Enter a name for your application, select Mobile/Desktop, and click Create.

    The Create Application form with Application Name, Application URL, and Select Application Type fields. Mobile/Desktop is selected.

  3. In the right panel, click + Setup a redirect URI and enter your application's callback URL.

    The redirect URI is where SecureAuth sends users after they sign in. For mobile apps, this is typically a custom URL scheme (for example, myapp://callback) rather than an https URL.

  4. Copy the Client ID from the right panel. You'll need it when configuring your application code.

    The registered application's Overview tab showing the Quickstart tab in the navigation, and the right panel with CLIENT ID and REDIRECT URI

Integrate with your application​

After creating the client in SecureAuth, use the Quickstart tab to get framework-specific integration code pre-filled with your application's configuration.

Open the Quickstart tab guide for step-by-step instructions, React Native code snippets, and a link to clone a full working example.

Test the integration​

  1. Launch your application on a device or emulator.
  2. Trigger the login flow.
  3. Verify that users are redirected to SecureAuth for authentication.
  4. After signing in, confirm users are redirected back to your application.

Next steps​