1:24 p.m.
Hi again,
@Rainer, thanks, that would be very helpful!
@Scott, the simple test setup I created (which has the same problem) uses the
internal_attributes.yaml as follows:
attributes:
eppn:
saml: [eduPersonPrincipalName]
swissEduPersonHomeOrganization:
saml: [swissEduPersonHomeOrganization]
user_id_from_attrs: [eppn]
user_id_to_attr: eppn
Cheers,
Hannah
On 7 Aug 2019, at 12:41, Rh at IDN <rh at
identinetics.com> wrote:
Hi Hannah
I did use the docker deployment, but I am using a custom attribute directory with custom
mappings, and these are not R&E related. I can share the configuration later off-list.
- Rainer
Von meinem iPhone gesendet
Am 07.08.2019 um 13:03 schrieb Scott Koranda
<skoranda at gmail.com>:
Hi,
Thanks anyway - I guess I’ll have to go down the
non-Docker route :)
I am sure it will work.
Can you send me your config files, specifically
internal_attributes.yaml?
Thanks,
Scott K
If anyone else has successfully added attributes to a docker deployment, please let me
know!
Cheers,
Hannah
_______________________________________________
satosa-users mailing list
satosa-users at lists.sunet.se
https://lists.sunet.se/listinfo/satosa-users On 7 Aug 2019, at 10:54, Scott Koranda
<skoranda at gmail.com> wrote:
Hi,
> I’m not totally sure what you mean by undefined. I’m using the docker
> setup where there seem to be separate files for SAML and Shibboleth
> attributes: saml_uri.py and shibboleth_uri.py.
Sorry, my bad. I do not use the Docker image from the SATOSA project. I
build my own and use different names for the files in the attribute maps
directory.
> The Swiss attributes seem to be correctly defined in saml_uri.py (you
> can see them at
>
https://github.com/IdentityPython/SATOSA/pull/270/files#diff-a97bd52d95d3b3…)
> SWISSEDUPERSON_OID = 'urn:oid:2.16.756.1.2.5.1.1.’
> SWISSEDUPERSON_OID+’4’=‘swissEduPersonHomeOrganization’
Yes, I agree. If your image/container is really using those versions of
the files then the mappings are properly defined.
> I made a simplified version of my config at (will send it to you
> directly on Slack).
Thanks,
Scott K