Proposal to resolve entities by role+protocol

[Marvin Addison]

On Wed, Dec 9, 2015 at 6:53 PM Brent Putman

> Maybe you didn't get a chance to look at it before I pulled it from 3.2.0,
> but I was probably 90-95% finished with the more generalized secondary
> indexing framework I had in mind.
>

Sorry, I never looked at it.


> And I had a good chunk of the specific endpoint indexing plugin impl done
> also, that does the indexing by sub-path segments for partial path matching
> like is discussed in IDP-701.
>

Partial matching would definitely provide a needed feature. I had convinced
myself that filtering by role and protocol was needed as well to prevent
collisions between SAML and CAS protocol entries.


> I think mostly what remained was deciding on what the endpoint index input
> criteria would look like - reuse existing multiple critieria or create a
> new compound Criterion holding data for just this case.
>

I think I'd need to know some of the new use cases to make a comment. I
like the idea of reusing what we have, but that's more of a design
philosophy than a practical recommendation.

Only reason why I pulled it was: We weren't going to actually use it in
> 3.2.0 (for neither your CAS stuff nor inbound SAML artifact binding). I
> didn't want to unnecessarily and prematurely commit to the APIs, without
> having a chance to really test them out "for real".
>

Well, I need _something_ for IDP-701, so I expect that would exercise the
APIs if nothing else.

Unless there was some specific reason why you didn't want to go this route,
> that's how I would prefer to proceed.
>

+1
I was in a hurry with pressure to resolve IDP-701 for an internal need at
Virginia Tech, but now that's been relieved by another solution, so your
proposed January time frame is good for me.

M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20151210/7280b096/attachment-0001.html>