GEANT OIDC plugin

[Cantor, Scott]

On 9/11/18, 9:34 AM, "dev on behalf of Tom Scavo" <dev-bounces at shibboleth.net on behalf of trscavo at gmail.com> wrote:

> That's an interesting idea. A sub claim value is any ASCII string
> (<=255 chars) so stuffing a scoped attribute in there is possible, I
> guess. The problem is that sub claim values are defined to be case
> sensitive.

We can generate case-safe values, and we do.
 
>- No allowance is made for stored IDs.

It has nothing to say about it any more than SAML does.

>- A computed ID depends on the client's Sector Identifier
> (sector_identifier_uri), which is a URL.

Yes, I'm aware they support affiliations, as do we, so that would just have to be factored back into the implementation in the same way the equivalent SAML feature already is, though I'm sure it's unused in OIDC just as it was in SAML. My concern is just whether having a suffix is inherently a problem, and I don't believe it is.

-- Scott