---
schema_version: "1"
id: f475f0025224c1a22bab2f4b24c69a3d6b8a60c23f724eeca4b89e7256a9b1d7
title: Connected App and OAuth Terminology
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/remoteaccess_terminology.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.remoteaccess_terminology.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2d9b585c8346e41ccd5d720f65b71c2f23933fb71e5ac54a885e375c317b02f4
description: What’s a token? Consumer? Callback URL? To better understand OAuth-enabled connected apps, familiarize yourself with a few terms.
products:
  - Security
  - Cross Cloud
release: "264"
---
# Connected App and OAuth Terminology

What’s a token? Consumer? Callback URL? To better understand OAuth-enabled connected apps, familiarize yourself with a few terms.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>All</strong> Editions</td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-identity-264-0-0-production-enus/699dab6f-8f1a-4662-b24f-6521d5b747f7/images/icon_note.png)

Note Connected apps creation is restricted as of Spring ‘26. You can continue to use existing connected apps during and after Spring ‘26. However, we recommend using [external client apps](https://help.salesforce.com/s/articleView?id=xcloud.external_client_apps.htm&language=en_US) instead. If you must continue creating connected apps, contact Salesforce Support.

See [New connected apps can no longer be created in Spring ‘26](https://help.salesforce.com/s/articleView?id=005228017&type=1&language=en_US) for more details.

Access Token

Instead of using the user’s Salesforce credentials, a consumer (connected app) can use an access token to gain access to protected resources on behalf of the user.

For OAuth 1.0.A, the access token must be exchanged for a session ID.

For OAuth 2.0, the access token is a session ID and can be used directly.

Authorization Code

Only used in OAuth 2.0 with the web server flow, the authorization code is a token that represents the access granted by the end user. The authorization code is used to obtain an access token and a refresh token. It expires after 15 minutes.

For OAuth 1.0.A, see [RequestToken](https://help.salesforce.com/s/articleView?id=xcloud.remoteaccess_terminology.htm&release=264.0.0&type=5).

Authorization Server

The authorization server is the server that authorizes a resource owner, and upon successful authorization, issues access tokens to the requesting consumer.

Callback URL

A callback URL is the URL that is invoked after OAuth authorization for the consumer (connected app). In some contexts, the URL must be a real URL that the client’s web browser is redirected to. In others, the URL isn’t actually used, but the value between your client app and the server (the connected app definition) must be the same. For example, you might want to use a value that identifies the app, such as https://MyCompany.Myapp.

Consumer

A consumer is the website or app that uses OAuth to authorize both the Salesforce user and itself on the user’s behalf. Referred to as `client` in OAuth 2.0.

Consumer Key

A consumer uses a key to identify itself to Salesforce. Referred to as `client_id` in OAuth 2.0.

Consumer Secret

A consumer uses a secret to establish ownership of the consumer key. Referred to as `client_secret` in OAuth 2.0.

OAuth Endpoint

OAuth endpoints are the URLs that you use to make OAuth authorization requests to Salesforce.

Nonce

Nonce is a number, often a random number, used during authorization to ensure that requests cannot be reused.

OAuth

Open Authorization (OAuth) is a standard, token-based protocol for authorization.

Refresh Token

Only used in OAuth 2.0, a consumer can use a refresh token to obtain a new access token, without having the end user approve the access again.

Request Token

Only used in OAuth 1.0.A, a consumer (connected app) can use a request token to obtain authorization from the end user. It exchanges the token for an access token.

For OAuth 2.0, see [Authorization Code](https://help.salesforce.com/s/articleView?id=xcloud.remoteaccess_terminology.htm&release=264.0.0&type=5).

Resource Owner

The resource owner is the entity (usually the end user) that grants access to a protected resource.

Resource Server

The resource server is the server that hosts the protected resource. Your Salesforce org is the resource server that protects your data.

Token Secret

A consumer uses this secret to establish ownership of a given token, both for request tokens and access tokens.

User

An individual who has a Salesforce login.

#### See Also

- [Authorize Apps with OAuth](https://help.salesforce.com/s/articleView?id=xcloud.remoteaccess_authenticate.htm&release=264.0.0&type=5 "OAuth is an open protocol that authorizes a client application to access data from a protected resource through the exchange of tokens. OAuth tokens are essentially permissions given to a client application.")