Skip to content

Commit

Permalink
Code review: update allowed_origins documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
akanstantsinau authored and dopry committed Oct 17, 2023
1 parent 8dc3ff1 commit f528338
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions docs/tutorial/tutorial_01.rst
Original file line number Diff line number Diff line change
Expand Up @@ -92,9 +92,11 @@ point your browser to http://localhost:8000/o/applications/ and add an Applicati
`https://www.getpostman.com/oauth2/callback`

* `Allowed origins`: Browser-based clients use Cross-Origin Resource Sharing (CORS) to request resources from origins other
than their own. You can provide list of origins that will have access to the token endpoint
of :term:`Authorization Server`. This setting controls only token endpoint and it is not related
with Django CORS Headers settings.
than their own. Provide space-separated list of allowed origins for the token endpoint.
The origin must be in the form of `"://" [ ":" ]`, such as `https://login.mydomain.com` or `http://localhost:3000`.
Query strings and hash information are not taken into account when validating these URLs.
This does not include the 'Redirect URIs' or 'Post Logout Redirect URIs', if those domains will also use the token
endpoint, they must be included in this list.

* `Client type`: this value affects the security level at which some communications between the client application and
the authorization server are performed. For this tutorial choose *Confidential*.
Expand Down

0 comments on commit f528338

Please sign in to comment.