SP's description vs entityID as URL

[Szerb, Tamas]

Hello,

As I see, the entityID is usually an URL to provide its easy to read and
uniqueness.

Checking the shibboleth-idp's (v2) docs in
https://wiki.shibboleth.net/confluence/display/SHIB2/IdPAuthUserPassLoginPage

the <idpui:serviceName/> is the only tag to represent the SP's entityID, or
is there any other way?

To have a description of the SP in its metadata, what would be the proper
way to represent it in the login page of IdP, while we'd keep the entityID
as URL for the given SP?

as I see, the <idpui:serviceName/> would fall back to DisplayName, then
ServiceName so if they're filled, I can't show the entityID, besides that
I'd like to show the SP's textual name. Is the proper solution to
use <idpui:organizationName> for that and creating in SP metadata the
related Organization/OrganizationName or OrganizationDIsplayName?

Thanks,

Tamas
--
VWOL
Tamas SZERB <toma at rulez.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151006/f067eef6/attachment.html>