11:56 a.m.
Dear Satosa Users,
I'm trying to create a ResponseMicroService which generates a subject identifier of
pairwise-id [1] from the eduPersonTargetedID provided by the Home Organization's IdP.
To avoid collisions, I want the input to the generator for the pairwise-id to contain
entityID + '!' + eduPersonTargetedID, but the Response Context doesn't appear
to contain the entityID of the originating IdP. Evidently I don't understand the model
which SATOSA uses to pass information from backend to frontend...
- Is there a way to access the proxied IdP's entityID from a ResponseMicroService?
- Would it be better to generate the attribute in a RequestMicroService?
- Do microservices act in the order that they're defined in proxy_conf.yaml? For
example, can I define a microservice to generate the new attribute from an existing
attribute, and then filter out the existing attribute.
Any information appreciated.
Thanks,
Alex
[1] SAML subject identifier attributes,
https://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/cs01/saml-su…
—
Alex Stuart
Principal technical support specialist (UK federation)
alex.stuart at jisc.ac.uk
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is
registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered
office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee
which is registered in England under company number 2881024, VAT number GB 197 0632 86.
The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.