> For a new SP we're being asked to provide attributes to it might be
> valuable to put some conditional processing within our attribute
> resolver. I note from an example I've seen of someone elses IdP
> that you can do things like access the entityID of the SP the user is
> currently accessing with:
> Googling this hasn't come up with much. Does anyone know, where is
this documented? How do I find out what else I can get to?
Is this not rather going around the houses?
If I'm not misunderstanding your goal, can you not just include
additional AttributeDefinitions with different ids in your
attribute-resolver.xml and then use different policies in the
attribute-filter.xml to ensure that the right ones go to the right SPs?
Steve Glover: SDSS, EDINA, Causewayside House, 160 Causewayside EH9 1PR
e:[log in to unmask] t:0131 650 2908 f:0131 650 3308 m:07961 446 902
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.