Back to Top

Authentication settings

System administrators can manage many ArcGIS Pro user application settings.

The settings below should be added under the Authentication element in the Pro.settingsConfig file. One set of AuthConnection elements is required for each authentication connection you want to manage.

Learn more about authentication options

AuthConnection

In the user interface, authentication connections appear on the Authentication tab on the Options dialog box. Each AuthConnection element must include all the elements that correspond to connection properties on the Add Connection dialog box.

An example of this setting for a Microsoft Entra ID connection type is shown below.

<Authentication>
  <AuthConnection isLocked="true">
	   <Name>ConnectionName</Name>
	   <Type>MicrosoftEntraID</Type>
	   <Environment>AzureGlobal</Environment>
	   <TenantID>example.domain.com</TenantID>
           <ClientID>123456789</ClientID>
           <Scopes>
	       <Scope>Scope1</Scope>
	       <Scope>Scope2</Scope>
	   </Scopes> 
  </AuthConnection>
</Authentication>

An example of this setting for a Custom connection type setting is shown below.

<Authentication>
  <AuthConnection isLocked="true">
	   <Name>ConnectionName</Name>
	   <Type>Custom</Type>
	   <AuthorizationURL>example.domain.com/oauth2/authorize</AuthorizationURL>
	   <TokenURL>example.domain.com/oauth2/token</TokenURL>
           <ClientID>123456789</ClientID>
           <Scopes>
	       <Scope>Scope1</Scope>
	       <Scope>Scope2</Scope>
	   </Scopes> 
  </AuthConnection>
</Authentication>

Name

In the user interface, this property corresponds to the Connection Name text box on the Add Connection dialog box.

Possible values are valid connection names. Connection names are limited to 50 characters and cannot contain a backslash ( \ ).

An example of this setting is shown below.

<Name>ConnectionName</Name>

Type

In the user interface, this property corresponds to the Type setting on the Add Connection dialog box.

Possible values are the following:

MicrosoftEntraID (Microsoft Entra ID)
Custom

An example of this setting is shown below.

<Type>MicrosoftEntraID</Type>

Environment

In the user interface, this property corresponds to the Azure Environment options on the Add Connection dialog box when the Type setting is Microsoft Entra ID.

Possible values are the following:

AzureGlobal (Azure)
AzureChina (Azure China)
AzureUSGovt (Azure US Government)

An example of this setting is shown below.

<Environment>AzureGlobal</Environment>

TenantID

In the user interface, this property corresponds to the Microsoft Entra Domain text box on the Add Connection dialog box when the Type setting is Microsoft Entra ID.

Possible values are Microsoft Entra ID domain names.

An example of this setting is shown below.

<TenantID>example.domain.com</TenantID>

ClientID

In the user interface, this property corresponds to the Client ID text box on the Add Connection dialog box.

Possible values are Client IDs for ArcGIS Pro.

An example of this setting is shown below.

<ClientID>123456789</ClientID>

AuthorizationURL

In the user interface, this property corresponds to the Authorization URL text box on the Add Connection dialog box when the Typesetting is Custom.

Possible values are URLs of the endpoints for obtaining authorization.

An example of this setting is shown below.

<AuthorizationURL>example.domain.com/oauth2/authorize</AuthorizationURL>

TokenURL

In the user interface, this property corresponds to the Token URL text box on the Add Connection dialog box when the Type setting is Custom.

Possible values are URLs of the endpoints for requesting an access token.

An example of this setting is shown below.

<TokenURL>example.domain.com/oauth2/token</TokenURL>

Scopes

In the user interface, this property corresponds to the Scopes text box on the Add Connection dialog box. Scopes are optional. If the Type setting is MicrosoftEntraID and no scope is specified, the scope https://storage.azure.com/.default is added to user machines by default.

Possible values are strings that specify the scope of the access request.

An example of this setting is shown below.

<Scopes>
    <Scope>Scope1</Scope>
    <Scope>Scope2</Scope>
</Scopes>

Feedback on this topic?

In this topic

AuthConnection