openstack/deb-python-pysaml2
Code Issues Proposed changes

Updated the attribute maps docs

Browse Source
This commit is contained in:
Baiju Muthukadan
2011-04-12 19:23:51 +05:30
parent 093d725745
commit c95dcc914e
1 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
doc/howto/config.rst
View File

@@ -62,32 +62,32 @@ Format::
"attribute_map_dir": "attribute-maps" "attribute_map_dir": "attribute-maps"
Points to a directory which has subdirectories, one per name-format you Points to a directory which has the attribute maps in Python modules.
expect to support. So a typical tree would be.:: A typical map file will looks like this::
attribute-maps MAP = {
| "identifier": "urn:oasis:names:tc:SAML:2.0:attrname-format:basic",
+-- urn:oases:names:tc:SAML:2.0:name-format:basic "fro": {
| | 'urn:mace:dir:attribute-def:aRecord': 'aRecord',
| +-- fro 'urn:mace:dir:attribute-def:aliasedEntryName': 'aliasedEntryName',
| +-- to 'urn:mace:dir:attribute-def:aliasedObjectName': 'aliasedObjectName',
| 'urn:mace:dir:attribute-def:associatedDomain': 'associatedDomain',
+-- urn:oases:names:tc:SAML:2.0:name-format:uri 'urn:mace:dir:attribute-def:associatedName': 'associatedName',
| ...
+-- fro },
+-- to "to": {
'aRecord': 'urn:mace:dir:attribute-def:aRecord',
The *to* and *fro* files then contain the mapping between the names. 'aliasedEntryName': 'urn:mace:dir:attribute-def:aliasedEntryName',
The start of the urn:oases:names:tc:SAML:2.0:name-format:uri/fro file 'aliasedObjectName': 'urn:mace:dir:attribute-def:aliasedObjectName',
for instance looks like this:: 'associatedDomain': 'urn:mace:dir:attribute-def:associatedDomain',
'associatedName': 'urn:mace:dir:attribute-def:associatedName',
...
}
}
{ The attribute map module contains a MAP dictionary with three items. The
'urn:oid:1.3.6.1.4.1.5923.1.1.1.2': 'eduPersonNickname', `identifier` item is the name-format you expect to support.
'urn:oid:1.3.6.1.4.1.5923.1.1.1.9': 'eduPersonScopedAffiliation', The *to* and *fro* sub-dictionaries then contain the mapping between the names.
'urn:oid:1.3.6.1.4.1.5923.1.1.1.11': 'eduPersonAssurance',
'urn:oid:1.3.6.1.4.1.5923.1.1.1.10': 'eduPersonTargetedID',
'urn:oid:1.3.6.1.4.1.5923.1.1.1.4': 'eduPersonOrgUnitDN',
'urn:oid:1.3.6.1.4.1.5923.1.1.1.1': 'eduPersonAffiliation',
As you see the format is again a python dictionary where the key is the As you see the format is again a python dictionary where the key is the
name to convert from and the value is the name to convert to. name to convert from and the value is the name to convert to.