Can a URI be used as an OIDC client ID?

[Wessel, Keith]

Hi, all,

In doing some work with Roberto from UIC for a multi-campus OIDC application, we tried to use a full URI as the client ID in our oidc-client.json:

"client_id": "https://app.example.edu"

The metadata resolver tries to look up a client with ID "https". It chops off everything starting with the colon.

Is this a bug or expected behavior?

We realize that, since it's not federation metadata, there's not a lot of value in using a URI as the client ID, but it does bring some bit of consistency between SAML and OIDC registrations.

Thanks,
Keith