V4 and OIDC client_names on the login page
Lipscomb, Gary
glipscomb at csu.edu.au
Sun Feb 14 21:54:16 UTC 2021
I have the same issue, any resolution yet.
Regards
Gary
-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Wessel, Keith
Sent: Saturday, 13 February 2021 08:07
To: users at shibboleth.net
Subject: V4 and OIDC client_names on the login page
Hi, all,
In V3, if a "client_name" attribute was set in an OIDC client's metadata, it would get picked up in login.vm:
#set ($serviceName = $rpUIContext.serviceName)
This worked for both the name of a SAML SP and an OIDC client.
In V4, it's still resolving to the service name for SAML SPs, but it's not seeming to pick up the client_name for OIDC clients. My login.vm is designed to display a service name if there is one or to fall back on the entityID if there isn't one. My IdP is displaying the client_id which, I believe, is because it's not picking up the client_name to mape to the service name.
Is there some other way I should be picking this up in login.vm, or is this a bug?
Thanks,
Keith
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list