Application Settings

On the Applications page of the Auth0 Dashboard, locate your Application and click its name to view the available settings.

Name: The name of your application. Editable, and will be seen in the portal, emails, logs, and so on.
Domain: Your Auth0 tenant name. You choose this when you create a new Auth0 tenant, and it cannot be changed. If you need a different domain, you must register for a new tenant by selecting + Create Tenant in the top-right menu.
Client ID: The unique identifier for your application. You will use this when configuring authentication with Auth0. Generated by the system when you create a new application and cannot be modified.
Client Secret: A string used to sign and validate ID Tokens for authentication flows and to gain access to select Auth0 API endpoints. By default, the value is hidden, so check the Reveal Client Secret box to see it. While the Client ID is considered public information, the Client Secret must be kept confidential. If anyone can access your Client Secret, they can issue tokens and access resources they shouldn't be able to access.
Description: A free-text description of the Application's purpose. Maximum of 140 characters.
Application Logo: The URL to a logo (recommended size: 150x150 pixels) to be displayed for the application. Appears in several areas, including the list of applications in the Dashboard and customized consent forms.
Application Type: The Auth0 application type. Determines which settings you can configure using the Dashboard. Not editable for M2M Apps. Sometimes disabled for other Auth0 application types if the selected grant types are only allowed for the currently selected application type.
Token Endpoint Authentication Method: Defines the requested authentication method for the token endpoint. Possible values are None (public client without a client secret), Post (client uses HTTP POST parameters), and Basic (client uses HTTP Basic). Only editable for Regular Web Apps and M2M Apps. You can provide up to 100 URLs in the Allowed Callback URLs, Allowed Web Origins, Allowed Logout URLs, Allowed Origins (CORS) fields.
Application Login URI: In some scenarios, Auth0 will need your application to start the OIDC login flow. This URI should point to a route in your application that starts the flow, by redirecting to the /authorize endpoint. It would usually take the form of https://myapp.org/login. See Configure Default Login Routes for details.
Allowed Callback URLs: Set of URLs to which Auth0 is allowed to redirect users after they authenticate. You can specify multiple valid URLs by comma-separating them (typically, to handle different environments like QA or testing). For production environments, verify that the URLs do not point to localhost. You can use the star symbol as a wildcard for subdomains (*.google.com). Make sure to specify the protocol (https://) otherwise, the callback may fail in some cases. With the exception of custom URI schemes for native clients, all callback URLs should use protocol https://.
Allowed Logout URLs: After a user logs out from Auth0 you can redirect them with the returnTo query parameter. The URL that you use in returnTo must be listed here. You can specify multiple valid URLs by comma-separating them. For production environments, verify that the URLs do not point to localhost. You can use the star symbol as a wildcard for subdomains (*.google.com). Notice that query strings and hash information are not taken into account when validating these URLs. See Logout.
Allowed Web Origins: List of URLs from where an authorization request using Cross-Origin Authentication, Device Flow, and web_message can originate from. You can specify multiple valid URLs by comma-separating them. For production environments, verify that the URLs do not point to localhost. You can use the star symbol as a wildcard for subdomains (*.google.com). Paths, query strings, and hash information are not taken into account when validating these URLs (and may, in fact, cause the match to fail).
Allowed Origins (CORS): Set of URLs that will be allowed to make requests from JavaScript to Auth0 API (typically used with CORS). This prevents same-origin policy errors when using Auth0 from within a web browser. By default, all your callback URLs will be allowed. This field allows you to enter other origins if you need to. You can specify multiple valid URLs by comma-separating them. For production environments, verify that the URLs do not point to localhost. You can use the star symbol as a wildcard for subdomains (*.google.com). Notice that paths, query strings, and hash information are not taken into account when validating these URLs (and may, in fact, cause the match to fail).
ID Token Expiration (seconds): The amount of time (in seconds) before the Auth0 ID Token expires. The default value is 36000, which maps to 10 hours.
Use Auth0 instead of the IdP to do Single Sign-on: If enabled, this setting prevents Auth0 from redirecting authenticated users with valid sessions to the identity provider (such as Facebook or ADFS). Legacy tenants only.

The Advanced Settings section allows you to:

Manage or add application metadata, device, OAuth, and WS-Federation settings
Obtain certificates and token endpoint information
Set the grant type(s) for the application

Dashboard - Applications - Advanced Settings

Application metadata are custom string keys and values (each of which has a character maximum of 255), set on a per-application basis. Metadata is exposed in the application object as client_metadata, and in rules as context.clientMetadata. You can create up to 10 sets of metadata.

If you're developing a mobile application, you can provide the necessary iOS/Android parameters here.

Dashboard - Applications - Advanced - Device Settings

When developing iOS apps, you'll provide your Team ID and App Bundle Identifier.
When developing Android apps, you'll provide your App Package Name and your Key Hashes.

Set the OAuth-related settings on this tab.

Dashboard - Applications - Advanced - OAuth Settings

By default, all apps/APIs can make a delegation request, but if you want to explicitly grant permissions to selected apps/APIs, you can do so in Allowed Apps/APIs.
Set the algorithm used (HS256 or RS256) for signing your JSON Web Tokens. See JSON Web Token Signing Algorithms for details. When selecting RS256 (recommended), the token will be signed with your tenant's private key. For a detailed overview of the JSON web token signing algorithms, see our blog post: JSON Web Token (JWT) Signing Algorithms Overview.
Toggle the Trust Token Endpoint IP Header setting; if this is enabled, the auth0-forwarded-for is set as trusted and used as a source of end user IP information for protection against brute-force attacks on the token endpoint. This setting is only available for Regular Web Apps and M2M Apps.
Toggle the switch to indicate if your application is OIDC Conformant or not. Applications flagged as OIDC Conformant will strictly follow the OIDC specification.
Set the location URL for Cross-Origin Verification Fallback. This is the location of the page that will be rendered inside an iframe to perform the token verification when third-party cookies are not enabled in the browser. Must be in the same domain where the embedded login form is hosted and must have an https scheme.

Select grant types to enable or disable for your application. Available grant types are based on the application type.

Dashboard - Applications - Advanced - Grant Types

Manage or add WS-Federation settings.

Dashboard - Applications - Advanced - WS-Federation

Manage or add the signing certificate, and its fingerprint and thumbprint.

Dashboard - Applications - Advanced - Certificates

View endpoint information for OAuth, SAML, and WS-Fed.

Dashboard - Applications - Advanced - Endpoints

Docs