Skip to content

Commit 4991c2c

Browse files
authored
Merge pull request #424 from dino8890/attributes-docs
Clarified attribute mapping docs.
2 parents 47e9997 + 9703cfa commit 4991c2c

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

docs/source/contents/setup.rst

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -379,12 +379,9 @@ SAML_ATTRIBUTE_MAPPING option in your settings.py::
379379
where the keys of this dictionary are SAML user attributes and the values
380380
are Django User attributes.
381381

382-
If you are using Django user profile objects to store extra attributes
383-
about your user you can add those attributes to the SAML_ATTRIBUTE_MAPPING
384-
dictionary. For each (key, value) pair, djangosaml2 will try to store the
385-
attribute in the User model if there is a matching field in that model.
386-
Otherwise it will try to do the same with your profile custom model. For
387-
multi-valued attributes only the first value is assigned to the destination field.
382+
For each (key, value) pair, djangosaml2 will try to store the attribute (key) in your
383+
configured `User` model if the matching fields exists on that model. For multi-valued
384+
attributes only the first value is assigned to the destination field.
388385

389386
Alternatively, custom processing of attributes can be achieved by setting the
390387
value(s) in the SAML_ATTRIBUTE_MAPPING, to name(s) of method(s) defined on a

0 commit comments

Comments
 (0)