Hi,
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?
Take a look at the ldap_attribute_store microservice for one example of
one way how to do what you need. Specifically see this
https://github.com/IdentityPython/SATOSA/blob/master/src/satosa/micro_servi…
On line 365 you will see how to resolve the entityID for the originating
SP, and on line 464 you will get a hint for how to resolve the entityID
for the authenticating IdP.
- Would it be better to generate the attribute in a
RequestMicroService?
Probably not since that would fire before the user is authenticated. You
could generate some of the information and store it in the context to be
later retrieved by your response microservice, but I do not think it is
worth the trouble.
- Do microservices act in the order that they're
defined in
proxy_conf.yaml?
Yes.
Thanks,
Scott K