Security and authentication

ArcGIS supports secure access to location services and private data. It ensures that only valid, authorized users and services access protected information. In order to access secure ArcGIS resources, you need an access token. To get an access token, you need to choose a type of authentication and implement an authentication workflow in your app. The type of authentication you use will depend on the security and access requirements of your app.

There are three types of authentication that you can use to get an access token:

API key authentication: grants a permanent token that grants your application access to ready-to-use services and, with an ArcGIS Developer account, private content.
User authentication (sometimes referred to as named user or ArcGIS Identity): a collection of authentication workflows that connect your app to a user's ArcGIS account.
- OAuth 2.0: manage ArcGIS authentication and grant a short-lived access token generated via OAuth 2.0. This gives your application permission to access ArcGIS secured services authorized to an existing ArcGIS user's account.
- Generate token: manages ArcGIS authentication and grants a short-lived access token generated via Esri's proprietary token-based authentication mechanism. This gives your application permission to access ArcGIS secured services authorized to an existing ArcGIS user's account.
- Network credential: manage network authentication (also known as web-tier authentication) for ArcGIS Enterprise. This gives your application permission to access network secured services authorized to your web-tier's identity store user accounts. Supports Public Key Infrastructure (PKI), Integrated Windows Authentication (IWA), Kerberos, and HTTP Basic/Digest.
App credential authentication: uses the registered application's credentials to access ready-to-use services on ArcGIS. It manages ArcGIS authentication and grants a short-lived access token generated via OAuth 2.0 using the application's client ID and client secret outside of the context of a user.

For more information, see Security and authentication in the Mapping APIs and location services guide.

Choose a type of authentication

The following considerations can help determine which type of authentication to implement:

Access to resources—Your app can access ready-to-use services using an API key, User authentication, or App credential authentication. To access private data hosted in ArcGIS Online or ArcGIS Enterprise, or content that requires an ArcGIS Online subscription, your app needs an authenticated user to sign in with their account.
User experience—If you don't want to make users log in, your app can access ready-to-use services using an API key or App credential authentication. In this case, users will not need to have an ArcGIS account in order to use your app.
Usage charges—If you want service usage to be charged to the user's account, your app must request that the user log in. When using an API key or App credential authentication, all access to services from your app will be charged to your developer account.

You might also need to consider the level of security required for your app, how your app will be distributed, and your available ArcGIS products and accounts.

Scenario	Solution
Your app requires access to ready-to-use services only, you don't want to make users log in, and you are willing to pay for all charges incurred from usage of the app.	API key or App credential authentication
Your app requires access to ready-to-use services only and you want usage charged to the user.	User authentication
Your app needs to access content that requires an ArcGIS Online subscription.	User authentication
Your app needs to access private hosted data on your ArcGIS Developer account.	API key or App credential authentication
Your app allows users to view and edit private data hosted in ArcGIS Online or ArcGIS Enterprise.	User authentication
You plan to distribute your app through ArcGIS Marketplace.	User authentication

API key authentication

An API key is a permanent access token that grants your public-facing application access to specific, ready-to-use services, and, with an ArcGIS Developer account, private content, items, and limited client referrers.

Use API keys when you want to:

Quickly write applications that consume ready-to-use services.
Provide access to services without requiring users to sign in with an ArcGIS account.
Use an access token that doesn't expire.

Learn more about API keys

Use API keys in your app

An API key can be used to authorize access to specific ArcGIS Online services and resources from your app, as well as to monitor access to those services. An API key is created and managed in the ArcGIS developer dashboard and is tied to your ArcGIS account.

You can set an API key on the ArcGISEnvironment, which will apply the key to all requests your app makes for ArcGIS Online services and resources.

You can also set an API key on any class that implements APIKeyResource. When you set an API key for a specific class, it will override any key you may have set on ArcGISEnvironment, enabling more granular usage telemetry and management for ArcGIS Online resources used by your app.

Classes that implement APIKeyResource include:

User authentication

User authentication is a set of authentication workflows that allow users with an ArcGIS account to sign into an application and access ArcGIS content, services, and resources. The typical authentication protocol used is OAuth2.0. When a user signs into an application with their ArcGIS account, an access token is generated that authorizes the application to access services and content on their behalf. The resources and functionality available depend on the user type, roles, and privileges of the user's ArcGIS account. This authentication type was previously known as Named user login and ArcGIS identity.

Services that your app accesses with user authentication will be billed to the authenticated user's ArcGIS account and its associated ArcGIS subscription. If your application will access your users' secure content in ArcGIS or if you plan to distribute your application through ArcGIS Marketplace, you must use user authentication.

Implement user authentication when you want to:

Ensure users are signed in and authenticated with their own ArcGIS account.
Use your app user's credits to pay for their private data, content, or service transactions.
Limit the length of time users can be signed in to your app with a temporary token.
Distribute your app through ArcGIS Marketplace.

Learn more about user authentication

App credential authentication

App credential authentication grants a short-lived access token, generated via OAuth 2.0, authorizing your application to access ready-to-use services, such as basemap layers, search, and routing.

Use app credential authentication when you want to:

Access ready-to-use services with a more secure process and a short-lived token.
Provide access to services without requiring users to have an ArcGIS account.

Learn more about app credential authentication

Authentication tool

In this SDK, all aspects of ArcGIS and network authentication have been encapsulated into a single ArcGIS Maps SDK for Swift toolkit component called the Authenticator. This component can handle several types of authentication challenges, such as ArcGIS authentication (token and OAuth), Integrated Windows Authentication (IWA), and Client Certificate (PKI), and provides default actions for login prompts, certificate selection prompts, and server trust prompts. For example, here is the default alert prompting the user for username and password credentials.

Authenticator LoginViewModifier to present a login alert

In the application's App struct, import the ArcGISToolkit, create an instance of the Authenticator, ensure that the application's AuthenticationManager uses it to handle authentication challenges. Set the authenticator view modifier so that a prompt can be displayed if the Authenticator is asked to handle an authentication challenge.

ContentView.swift
Use dark colors for code blocksCopy

import SwiftUI
import ArcGIS
import ArcGISToolkit

struct AuthenticationApp: App {

    @ObservedObject var appAuthenticator: Authenticator

    init() {
        // Creates an authenticator object.
        appAuthenticator = Authenticator()
        // Sets the authenticator to handle authentication challenges.
        ArcGISEnvironment.authenticationManager.handleChallenges(using: appAuthenticator)
    }

    var body: some SwiftUI.Scene {
        WindowGroup {
            ContentView()
            // Sets the authenticator view modifier.
                .authenticator(appAuthenticator)

        }
    }
}

You can also configure the Authenticator to persist credentials in the keychain. If the app is restarted, the store of credentials is automatically pre-populated with saved credentials and the user does not have to sign in again.

ContentView.swift
Use dark colors for code blocksCopy
                .task {
                    try? await ArcGISEnvironment.authenticationManager.setupPersistentCredentialStorage(
                        access: .whenUnlockedThisDeviceOnly,
                        synchronizesWithiCloud: false
                    )
                }

During application sign-out you should revoke all OAuth user tokens then clear all credentials from the credentials stores.

ContentView.swift
Use dark colors for code blocksCopy
        // Revokes OAuth refresh and access tokens
        await ArcGISEnvironment.authenticationManager.revokeOAuthTokens()
        // Clears all ArcGIS and network credentials from their respective stores.
        await ArcGISEnvironment.authenticationManager.clearCredentialStores()

To see the Authenticator in action, check out the Authentication Example application and refer to AuthenticationApp.swift in your project.

Authentication manager

If you want to manage the authentication process yourself, use the AuthenticationManager that is available as a static property on the ArcGISEnvironment.

Use dark colors for code blocksCopy
        let authenticationManager = ArcGISEnvironment.authenticationManager

The AuthenticationManager provides:

ArcGIS and network challenge handlers that allow you to respond to the authentication challenges. For example, you can write code to present the user with a login screen and then continue to authenticate with those credentials. For more information, see Handle authentication challenges.
The credential stores are available for you to place ArcGIS and network credentials that are automatically checked when your application attempts to connect to secure resources. These stores can also be made persistent in the keychain so that user does not have to sign in again when the application is re-launched. For more information, see Create and store credentials.

Handle authentication challenges

If your application attempts to access a secure resource and there is no matching credential in the credential store, an authentication challenge is raised:

ArcGISAuthenticationChallenge is raised if the ArcGIS secured resource requires OAuth or ArcGIS Token authentication.
NetworkAuthenticationChallenge is raised if the ArcGIS secured resource requires network credentials, such as Integrated Windows Authentication (IWA) or Public Key Infrastructure (PKI).

Catch and respond to these authentication challenges using the ArcGISAuthenticationChallengeHandler and NetworkAuthenticationChallengeHandler, respectively. These challenge handlers are protocols that you can adopt in any class, structure, or other type.

ArcGIS authentication challenge handler

The ArcGISAuthenticationChallengeHandler is used to handle authentication challenges from ArcGIS secured resources that require OAuth or ArcGIS Token authentication. Handle the challenge by returning the ArcGISAuthenticationChallenge.Disposition. It has the following options:

continueWithCredential(ArcGISCredential) - Continue the challenge with the given credential.
continueWithoutCredential - The request that issued the authentication challenge will fail with the challenge's error.
cancel - The request that issued the authentication challenge will fail with CancellationError.

Create a class adopting the ArcGISAuthenticationChallengeHandler protocol to handle ArcGIS authentication challenges.

Use dark colors for code blocksCopy
@MainActor
// Creates an ArcGIS authentication challenge handler
final class MyArcGISChallengeHandler: ArcGISAuthenticationChallengeHandler {
    // The OAuth configurations that this challenge handler can work with.
    let oAuthUserConfigurations: [OAuthUserConfiguration]
    public init(
        oAuthUserConfigurations: [OAuthUserConfiguration] = []
    ) {
        self.oAuthUserConfigurations = oAuthUserConfigurations
    }

    // Handles the challenge to an ArcGIS secured resource that requires OAuth or ArcGIS Token authentication.
    func handleArcGISAuthenticationChallenge(
        _ challenge: ArcGISAuthenticationChallenge
    ) async throws -> ArcGISAuthenticationChallenge.Disposition {
        // If an OAuth user configuration is available for the challenge then create an `OAuthUserCredential`.
        if let configuration = oAuthUserConfigurations.first(where: { $0.canBeUsed(for: challenge.requestURL) }) {
            return .continueWithCredential(
                try await OAuthUserCredential.credential(for: configuration)
            )
        } else {
            // If not, prompt the user for a username and password to create a `TokenCredential`.
            // ...
            return .continueWithCredential(
                try await TokenCredential.credential(for: challenge, username: "username", password: "password")
            )
        }
    }
}

Set an instance of the class on the AuthenticationManager.arcGISAuthenticationChallengeHandler property of the ArcGISEnvironment.

Use dark colors for code blocksCopy
        let myArcGISChallengeHandler = await MyArcGISChallengeHandler(
            oAuthUserConfigurations: [
                OAuthUserConfiguration(
                    portalURL: URL(string: "portal-string")!,
                    clientID: "client-ID",
                    redirectURL: URL(string: "redirect-string")!
                )
            ]
        )

Network authentication challenge handler

The NetworkAuthenticationChallengeHandler is used to handle authentication challenges from ArcGIS secured resources that require network credentials, such as Integrated Windows Authentication (IWA) or Public Key Infrastructure (PKI). Handle the challenge by returning the NetworkAuthenticationChallenge.Disposition. It has the following options:

continueWithCredential(NetworkCredential) - Continue the challenge with the given credential.
continueWithoutCredential - The request that issued the authentication challenge will fail with the challenge's error.
cancel - The request that issued the authentication challenge will fail with CancellationError.

Create a class adopting the NetworkAuthenticationChallengeHandler protocol to handle Network authentication challenges.

Use dark colors for code blocksCopy
// Creates a Network authentication challenge handler
final class MyNetworkChallengeHandler: NetworkAuthenticationChallengeHandler {
    func handleNetworkAuthenticationChallenge(
        _ challenge: NetworkAuthenticationChallenge
    ) async -> NetworkAuthenticationChallenge.Disposition {
        switch challenge.kind {
        case .ntlm, .basic, .digest:
            // Prompts the user for a username and password to create a `NetworkCredential`.
            // ...
            return .continueWithCredential(.password(username: "username", password: "password"))
        case .clientCertificate:
            // Prompts the user for a client certificate to create a `NetworkCredential`.
            // ...
            do {
                return .continueWithCredential(try .certificate(at: URL(fileURLWithPath: "/pathToCertificate"), password: "password"))
            } catch {
                return .continueWithoutCredential
            }
        case .serverTrust:
            // Prompts user to ask if they want to trust an untrusted host.
            // ...
            return .continueWithCredential(.serverTrust)
        @unknown default:
            return .cancel
        }
    }
}

Set an instance of the class on the AuthenticationManager.networkAuthenticationChallengeHandler property of the ArcGISEnvironment.

Use dark colors for code blocksCopy
    // Creates the challenge handler and set it on the `AuthenticationManager`.
    let myNetworkChallengeHandler = MyNetworkChallengeHandler()
    ArcGISEnvironment.authenticationManager.networkAuthenticationChallengeHandler = myNetworkChallengeHandler

Create and store credentials

You can create a credential in the authentication challenge handler when an authentication challenge is raised. See Handle authentication challenges for more information. Store these credentials in ArcGIS and network credential stores provided by the AuthenticationManager.

ArcGISCredentialStore stores ArcGIS credentials.
NetworkCredentialStore stores Network credentials.

These credential stores exist for the lifetime of the application and ensure that an authentication challenge is not raised if a matching credential exists in the store. If you want to avoid prompting users for credentials between application sessions, make them persisent in the keychain by setting the store instances created using the function makePersistent(access:synchronizesWithiCloud:) on the authentication manager.

Use dark colors for code blocksCopy
        ArcGISEnvironment.authenticationManager.arcGISCredentialStore = try await .makePersistent(
            access: .afterFirstUnlockThisDeviceOnly,
            synchronizesWithiCloud: true
        )
        await ArcGISEnvironment.authenticationManager.setNetworkCredentialStore(
            try await .makePersistent(access: .afterFirstUnlockThisDeviceOnly, synchronizesWithiCloud: true)
        )

During application sign-out you should revoke all OAuth user tokens and then clear all credentials from the credential stores.

Use dark colors for code blocksCopy
        // Iterates through the collection of `OAuthUserCreedential` objects stored in the `ArcGISCredentialStore`.
        // Revokes the refresh and access token of each `OAuthUserCredential`.
        try await oAuthUserCredential.revokeToken()

        // Clears all ArcGIS and network credentials from their respective stores.
        ArcGISEnvironment.authenticationManager.arcGISCredentialStore.removeAll()
        await ArcGISEnvironment.authenticationManager.networkCredentialStore.removeAll()

ArcGIS credentials

You can access secured resources with user authentication or app credential authentication using the following credential types.

OAuthUserCredential - A credential object used to access OAuth token-secured ArcGIS resources with a specific OAuthUserConfiguration.
OAuthApplicationCredential - A credential object used to access OAuth token-secured ArcGIS resources using the application's credentials.
TokenCredential - A credential object used to access token-secured ArcGIS resources.
PregeneratedTokenCredential - A credential object used to access token-secured ArcGIS resources using a token that is generated outside of your application.

If you know the services domain/server context, you can create an ArcGIS credential, independent of loading the specific resource and store it in the ArcGISCredentialStore.

OAuthUserCredential

To create an OAuthUserCredential, provide an OAuthUserConfiguration with a valid portal URL, client ID, and redirect URL. This will present the OAuth login page for the user to enter their username and password. Once the OAuthUserCredential is created, you will be able to access token information from the asynchronous tokenInfo property.

Use dark colors for code blocksCopy
        let configuration = OAuthUserConfiguration(
            portalURL: URL(string: "portal-string")!,
            clientID: "client-ID",
            redirectURL: URL(string: "redirect-string")!
        )
        let credential = try await OAuthUserCredential.credential(for: configuration)
        let tokenInfo = try await credential.tokenInfo

OAuthApplicationCredential

To create an OAuthApplicationCredential, provide a valid portal URL, a client ID, and a client secret. Optionally, you can specify the token expiration in minutes. Once the OAuthApplicationCredential is created, you will be able to access the token information from the asynchronous tokenInfo property.

Use dark colors for code blocksCopy
        let credential = try await OAuthApplicationCredential.credential(
            for: URL(string: "portal-string")!,
            clientID: "client-ID",
            clientSecret: "client-secret",
            tokenExpirationMinutes: 5
        )
        let tokenInfo = try await credential.tokenInfo

TokenCredential

To create a TokenCredential, provide a secured service URL, valid username, and password. Optionally, you can specify token expiration minutes. Once a TokenCredential is created, you will be able to access token information from the asynchronous tokenInfo property.

Use dark colors for code blocksCopy
        let credential = try await TokenCredential.credential(
            for: URL(string: "portal-string")!,
            username: "username",
            password: "password",
            tokenExpirationMinutes: 5
        )
        let tokenInfo = try await credential.tokenInfo

PregeneratedTokenCredential

To create a PregeneratedTokenCredential, provide a previously generated short or long-lived access token. Use this credential when the access token is created using the generateToken REST endpoint directly. You must provide the referer if one was used while generating the token.

Use dark colors for code blocksCopy
        let tokenInfo = TokenInfo(
            accessToken: "<access-token",
            expirationDate: date,
            isSSLRequired: true
        )
        let credential = PregeneratedTokenCredential(
            url: URL(string: "service-string")!,
            tokenInfo: tokenInfo!,
            referer: "referer"
        )

Network credentials

You can access resources secured by network authentication using the following credential types.

PasswordCredential - A credential object that is used to authenticate HTTP Basic/Digest or Integrated Windows Authentication (IWA) secured resources.
CertificateCredential - A credential object that is used to authenticate Client Certificate (PKI) secured resources.
NetworkCredential.serverTrust - A network credential that specifies that a server should be trusted.

PasswordCredential

The PasswordCredential is used to authenticate HTTP Basic/Digest, Integrated Windows Authentication (IWA) secured resources. To create a PasswordCredential, use a static function of NetworkCredential with username and a password.

Use dark colors for code blocksCopy
        // Password credential for HTTP Basic/Digest, Integrated Windows Authentication (IWA)
        let passwordCredential = NetworkCredential.password(username: "my-username", password: "my-password")

CertificateCredential

A CertificateCredential is used to authenticate Public Key Infrastructure (PKI) secured resources. To create a CertificateCredential, use a static function of NetworkCredential with the URL to a .p12 or .pfx extension certificate file on disk and a password.

Use dark colors for code blocksCopy
        let credential = try NetworkCredential.certificate(at: URL(fileURLWithPath: "file URL to .p12 or .pfx file"), password: "password")

ServerTrust

To trust a development server that uses a self-signed certificate (untrusted host), create a NetworkCredential and specify that the server should be trusted.

Use dark colors for code blocksCopy
        // Server trust credential for host with self-signed certificate
        let credential = NetworkCredential.serverTrust