trustchain-oc1-orchestral/authentik
Archived
10
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
This repository has been archived on 2024-05-31. You can view files and clone it, but cannot push or open issues or pull requests.
authentik/docs/property-mappings/index.md
Jens L 73116b9d1a
policies/expression: migrate to raw python instead of jinja2 (#49) 
* policies/expression: migrate to raw python instead of jinja2

* lib/expression: create base evaluator, custom subclass for policies

* core: rewrite propertymappings to use python

* providers/saml: update to new PropertyMappings

* sources/ldap: update to new PropertyMappings

* docs: update docs for new propertymappings

* root: remove jinja2

* root: re-add jinja to lock file as its implicitly required
2020-06-05 12:00:27 +02:00

1,007 B
Raw Blame History

Property Mappings

Property Mappings allow you to pass information to external Applications. For example, pass the current user's Groups as a SAML Parameter. Property Mappings are also used to map Source fields to passbook fields, for example when using LDAP.

SAML Property Mapping

SAML Property Mappings allow you embed Information into the SAML AuthN Request. THis Information can then be used by the Application to assign permissions for example.

You can find examples here

LDAP Property Mapping

LDAP Property Mappings are used when you define a LDAP Source. These Mappings define which LDAP Property maps to which passbook Property. By default, these mappings are created:

  • Autogenerated LDAP Mapping: givenName -> first_name
  • Autogenerated LDAP Mapping: mail -> email
  • Autogenerated LDAP Mapping: name -> name
  • Autogenerated LDAP Mapping: sAMAccountName -> username
  • Autogenerated LDAP Mapping: sn -> last_name

These are configured for the most common LDAP Setups.