OAuth2
The OAuth2 tab in the Internet panel, shows settings for the OAuth2 (Open Authorization) standard.
OAuth 2.0 is an authorization framework that allows applications to access services (such as email, cloud storage, or APIs) on a user’s behalf without handling the user’s password. Instead of sharing credentials, the user signs in through a trusted identity provider (for example, Google, Microsoft, or others), which then issues a time-limited access token to the application (such as PANTHEON). This token grants only the permissions that were approved by the user or administrator.
This approach is more secure, as passwords are not stored and access can be revoked at any time, supports multi-factor authentication, and is now the standard required by Microsoft as basic authentication is being phased out.
The tab can be accessed from the menu Settings | Program | Administration Panel by clicking the panel Settings | Internet and then the tab OAuth2.
 |
HINT
The labels in brackets next to the settings fields indicate the level on which setting applies:
- (c) – Company-level setting.
- (u) – User-level setting.
- (m) – Workstation-level setting.
|
|
Auth URL
|
Enter the Auth web address (URL) to provider's login endpoint that opens the sign-in page. Users log in here and grant permission for the application to access their mailbox.
|
|
Token URL
|
Enter the web address (URL) to endpoint that is used byprovider to issue access tokens. After a successful login, it returns a token proving the application is authorized to access email services.
|
|
Redirect URL
|
Enter the redirect URI or URL of the response. This refers to the location to which the authorization server redirects the user when the application has been successfully authorized and has been assigned an authorization code or access token.
|
|
Client ID
|
Enter the client ID. This is an application-related ID that helps authenticate the client/server OAuth 2.0 for ArcGIS client APIs. Developers create the Client ID by defining the application in their developer dashboard.
For more information, see https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/.
|
|
Client token
|
Enter the name of the customer token. It is used by server-side applications.
For desktop applications using Authorization Code with PKCE, this field is usually left empty, which is correct and recommended.
|
|
Scope
|
Enter the range or permission set on the token in the field. This is the context in which this token can operate. For more information, see https://oauth.net/2/scope/.
|
|
State
|
A security value to prevent request forgery. For desktop applications, it is often optional and can be left empty or set to a simple random string.
|