Security and authentication

The ArcGIS Platform supports secure access to location services and private data. It ensures that only valid, authorized users and services access protected information. To access secure resources, you need to implement an authentication method so your applications can make authenticated requests to services.

An authentication method is the process used obtain an access token. Your app must present an access token whenever it makes an authenticated request to location services. Access tokens define the scope and permissions available to your application. The authentication method you use to get an access token will vary.

There are three kinds of access tokens:

  • API key: permanent token that grants your application access to ready-to-use services and, with an ArcGIS Developer account, private content.
  • ArcGIS identity: temporary token that gives your application access to the private content and services authorized to an existing ArcGIS user's account.
  • Application credentials: temporary token generated via OAuth 2.0 that can authorize access to ready-to-use services.

To make authenticated requests to services, you need to set the token parameter to an access token.

ArcGIS identity

An ArcGIS identity, also known as a named user login, is a temporary access token that gives your application access to the content and services authorized to your application user's existing ArcGIS Online or ArcGIS Enterprise account. This temporary token is created using OAuth 2.0 protocol and authorizes your application to act on the user's behalf without revealing their secure password to your application. Service credits consumed are billed to the authenticated user's ArcGIS subscription and, during the authenticated period, your app is allowed to access private user content on the user's behalf.

Use ArcGIS identity 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 ArcGIS identity

API keys

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 ArcGIS Runtime 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 ArcGISRuntimeEnvironment, 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 ArcGIS Runtime class that implements IApiKeyResource. When you set an API key for a specific class, it will override any key you may have set on ArcGISRuntimeEnvironment, enabling more granular usage telemetry and management for ArcGIS Online resources used by your app.

Classes that implement IApiKeyResource include:

Application credentials

Application credentials are a short-lived access token obtained via OAuth 2.0 that allow access to ready-to-use services such as basemap layers, search, and routing.

Use application credentials when you want to:

  • Access ready-to-use services but want a more secure process with a short-lived token.
  • Provide access to services without requiring users to have an ArcGIS account.
Learn more about Application credentials

Choose an authentication method

The choice of which type of authentication to implement is mostly dependent upon the resources required by your application. Also consider the strengths and limitations of the API or SDK technology on which your application is built. Your choice of authentication method is also affected by the API with which you build your application. ArcGIS APIs contain a built in IdentityManger or AuthenticationManager, which provide helper methods and patterns for implementing ArcGIS identity workflows.

You are building an app that only requires access to ready-to-use services, such as the basemap layer, geocoding, or routing services.API key
You are building an app that allows users to view and edit private data in ArcGIS Platform.ArcGIS identity
You are building an application on a web server or API backend that only requires access to basemaps and geocoding.Application credentials
You are building an application using Esri Leaflet, Mapbox GL JS, or OpenLayers.API key
You are building an application using an ArcGIS API.API key or ArcGIS identity

Authentication manager

ArcGIS APIs contain a built-in AuthenticationManager, which provides helper methods and patterns for implementing ArcGIS identity workflows.

The AuthenticationManager is a singleton class that, when enabled, will manage the user credentials for the following resources:

  • ArcGIS Server resources secured using token-based authentication or using HTTP authentication. Note that only ArcGIS Server versions 10 SP 1 and greater are supported.
  • Secured resources (web maps, for example).
  • Secured ArcGIS Portal resources.

A credential for accessing to an ArcGIS resource can be preset by using AddCredential(). In this case the credential is used for any requests to the specified resources.

If a request to an ArcGIS resource returns an authorization error, the AuthenticationManager.ChallengeHandler, if not null, is called. This challenge handler can return the credential for accessing to the resource.

If the IChallengeHandler is null or if it doesn't return any credential, the authorization error is returned to the caller as if the request was executed out of the AuthenticationManager.

What's Next?

For more information about Security and Authentication, see the Security and Authentication chapter.


Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.