Skip to main content
Version: Release 1 - 1.1.3.X

Authentication Profile Variables

When configuring authentication profiles in Maptaskr Power Maps, you will encounter various variables that are essential for establishing secure connections to external map services. These variables include API keys, client secrets, and other credentials that are required by different authentication methods.

ArcGIS Online

ArcGIS is one of the most utilised authentication providers in Maptaskr Power Maps, and it supports multiple authentication methods. Depending on your specific requirements and the level of security needed, you can choose from the following authentication options:

Details about the different authentication flows supported by ArcGIS can be found in the official ArcGIS documentation: User Authentication Flows

Authorization code with PKCE

This method is a secure way to authenticate users without exposing sensitive credentials. It involves a two-step OAuth process where the client first obtains an authorization code and then exchanges it for an access token. This flow is particularly suitable for applications that require user interaction and long-term access.

This authentication profile template uses the variables:

Variable NameDescriptionExample Value
clientIdThe Client ID of your ArcGIS Online application.your-client-id

Details about this authentication flow can be found in the official ArcGIS documentation: Authorization code flow with PKCE

Client ID and Secret

This method allows you to authenticate using a Client ID and Client Secret, which are typically associated with an application registered in ArcGIS Online. It is a common approach for server-to-server authentication but requires careful handling of the Client Secret to ensure security. This authentication method is great for the Maptaskr Power Maps Flows connector, as it allows for secure server-to-server authentication without user interaction.

This authentication profile template uses the variables:

Variable NameDescriptionExample Value
clientIdThe Client ID of your ArcGIS Online application.your-client-id
clientSecretThe Client Secret of your ArcGIS Online application.your-client-secret

Details about this authentication flow can be found in the official ArcGIS documentation: Client credentials flow

Username and Password

Equivalent to the Generate token user flow, this method allows you to authenticate using your ArcGIS Online username and password. It is a straightforward approach but may not be the most secure option, especially for applications that require long-term access.

This authentication profile template uses the variables:

Variable NameDescriptionExample Value
usernameYour ArcGIS Online username.your-username
passwordYour ArcGIS Online password.your-password

Details about this authentication flow can be found in the official ArcGIS documentation: Generate Token

API Key

This method allows you to authenticate using an API Key, which is a simple and secure way to access ArcGIS Online services without exposing your username and password.

This authentication profile template uses the variables:

Variable NameDescriptionExample Value
apikeyYour ArcGIS Online API Key.your-api-key

Details about this authentication flow can be found in the official ArcGIS documentation: API Key authentication

ArcGIS Enterprise

Authorization code with PKCE

Similar to the ArcGIS Online Authorization code with PKCE flow, this method uses a two-step OAuth process that allows you to authenticate users securely without exposing sensitive credentials. It is designed for applications that require user interaction and long-term access to ArcGIS Enterprise services.

This authentication profile template uses the variables:

Variable NameDescriptionExample Value
YOUR_PORTAL_URLThe URL of your ArcGIS Enterprise portal.https://your-portal-url.com/arcgis
clientIdThe Client ID of your ArcGIS Enterprise application.your-client-id

Details about this authentication flow can be found in the official ArcGIS documentation: Authorization code flow with PKCE

Client ID and Secret

Similar to the ArcGIS Online Client ID and Secret flow, this method allows you to authenticate using a Client ID and Client Secret, which are typically associated with an application registered in ArcGIS Enterprise. It is a common approach for server-to-server authentication but requires careful handling of the Client Secret to ensure security. This authentication method is great for the Maptaskr Power Maps Flows connector, as it allows for secure server-to-server authentication without user interaction.

This authentication profile template uses the variables:

Variable NameDescriptionExample Value
YOUR_PORTAL_URLThe URL of your ArcGIS Enterprise portal.https://your-portal-url.com/arcgis
clientIdThe Client ID of your ArcGIS Enterprise application.your-client-id
clientSecretThe Client Secret of your ArcGIS Enterprise application.your-client-secret

Details about this authentication flow can be found in the official ArcGIS documentation: Client credentials flow

Username and Password

Similar to the ArcGIS Online username and password (Generate Token) flow, this method allows you to authenticate using your ArcGIS Enterprise username and password. It is a straightforward approach but may not be the most secure option, especially for applications that require long-term access.

This authentication profile template uses the variables:

Variable NameDescriptionExample Value
YOUR_PORTAL_URLThe URL of your ArcGIS Enterprise portal.https://your-portal-url.com/arcgis
usernameYour ArcGIS Enterprise username.your-username
passwordYour ArcGIS Enterprise password.your-password

Details about this authentication flow can be found in the official ArcGIS documentation: Generate Token

Azure Maps

Azure Maps is another popular authentication provider in Maptaskr Power Maps, and it primarily uses Subscription Keys for authentication.

Subscription Key

This method allows you to authenticate using a Subscription Key, which is a simple and secure way to access Azure Maps services without exposing your username and password.

This authentication profile template uses the variable:

Variable NameDescriptionExample Value
subscriptionKeyYour Azure Maps Subscription Key.your-subscription-key

Details about this authentication flow can be found in the official Azure Maps documentation: Authentication and authorization