Contexts and attribute operations

[Cantor, Scott]

On 1/6/14, 10:02 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>Right - but this means that we cannot inject the strategy as part of the
>filter definition creation.  If we put it there, then once the filter is
>configured and initialized there will be only one way to get from a
>FilterContext to a SAMLMetadatContext.  So the strategy has to be injected
>when the flow is put together.  This is where we currently inject the
>strategies for locating the SubjectContext and RelyingPartyContext.  But
>this in turn means that the only place we have to put information which
>the
>filters can see is the FilterContext.

I see what you mean.

>So we then have two options - just put the information we may need
>(entityID, SSOEndpoint) directly into the FilterContext -  just as we do
>for
>Principal and so forth, or put a strategy into the FilterContext being how
>to get from itself to the SAMLMetadatContext - the latter is slightly more
>cumbersome but would save cycles in the general case where we don't care
>about the SP's metadata, hence I favour it.

I favor that also, that makes sense. Then it's just naturally the profile
action populating this.

-- Scott