Skip to content

Commit 61970a9

Browse files
akanstantsinaudopry
authored andcommitted
Code review: update allowed_origins documentation
1 parent 37fe08c commit 61970a9

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/tutorial/tutorial_01.rst

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -92,9 +92,11 @@ point your browser to http://localhost:8000/o/applications/ and add an Applicati
9292
`https://www.getpostman.com/oauth2/callback`
9393

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

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

0 commit comments

Comments
 (0)