thanks Ivan that was very helpful!
On 03-05-18 14:38, Ivan Kanakarakis wrote:
Hello,
On 3 May 2018 at 12:28, Niels van Dijk <niels.vandijk at surfnet.nl> wrote:
Hi all,
I would like to mint a new attribute scheme called voPerson
(
https://voperson.org/) for use in a SaToSa? What would be the best
approach?
Please read this email/thread:
https://lists.sunet.se/pipermail/satosa-dev/2018-February/000183.html
SATOSA is not concerned with the attributes themselves. It is pysaml2
that handles them. SATOSA is only concerned with how attributes are
translated/mapped from one protocol to (an internal name, to) another
(and sometimes the same) protocol.
Attributes should be defined in a "MAP-structure" as seen under the
src/saml2/attributemaps directory:
https://github.com/IdentityPython/pysaml2/tree/f8e3468/src/saml2/attributem…
Once you have such a structure, you can point to a folder holding it
with the attribute_map_dir configuration option:
https://github.com/IdentityPython/pysaml2/blob/6a7c7fa/doc/howto/config.rst…
Note! that the default attribute maps will not be used if you define
the attribute_map_dir option - ie under the path that you will define,
you have to place all other attribute files that you will use (ie copy
over the saml_uri.py to be able to use saml attributes, etc)
Ofcourse, you can make a PR to include the voperson attributes in the
default attributemaps ;)
Cheers,
--
Niels van Dijk Technical Product Manager Trust & Security
Mob: +31 651347657 | Skype: cdr-80 | PGP Key ID: 0xDE7BB2F5
SURFnet BV | PO.Box 19035 | NL-3501 DA Utrecht | The Netherlands