22 lines
1017 B
Markdown
22 lines
1017 B
Markdown
|
# 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](integrations/)
|
||
|
|
|
||
|
|
## 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.
|