You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/settings_ref.rst
+22-3Lines changed: 22 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -262,6 +262,25 @@ example
262
262
The group doesn't need to exist in Django for this to work. This will work as long as it's in the groups claim
263
263
in the access token.
264
264
265
+
GUEST_USERNAME_CLAIM
266
+
--------------------
267
+
* **Default**: ``None``
268
+
* **Type**: ``string``
269
+
270
+
When these criteria are met:
271
+
272
+
1. A ``guest_username_claim`` is configured
273
+
2. Token claims do not have the configured ``settings.USERNAME_CLAIM`` in it
274
+
3. The ``settings.BLOCK_GUEST_USERS`` is set to ``False``
275
+
4. The claims ``tid`` does not match ``settings.TENANT_ID``
276
+
277
+
Then, the ``GUEST_USERNAME_CLAIM`` can be used to populate a username, when the ``USERNAME_CLAIM`` cannot be found in
278
+
the claims.
279
+
280
+
This can be useful when you want to use ``upn`` as a username claim for your own users,
281
+
but some guest users (such as normal outlook users) don't have that claim.
282
+
283
+
265
284
LOGIN_EXEMPT_URLS
266
285
-----------------
267
286
* **Default**: ``None``
@@ -423,13 +442,13 @@ The value of the claim must be a unique value. No 2 users should ever have the s
423
442
.. NOTE::
424
443
You can find the short name for the claims you configure in the ADFS management console underneath
425
444
**ADFS** ➜ **Service** ➜ **Claim Descriptions**
426
-
427
-
445
+
446
+
428
447
.. _version_setting:
429
448
430
449
VERSION
431
450
--------------
432
-
* **Default**: ``v1.0``
451
+
* **Default**: ``v1.0``
433
452
* **Type**: ``string``
434
453
435
454
Version of the Azure Active Directory endpoint version. By default it is set to ``v1.0``. At the time of writing this documentation, it can also be set to ``v2.0``. For new projects, ``v2.0`` is recommended. ``v1.0`` is kept as a default for backwards compatibility.
0 commit comments