> Thoughts on making this something that's always available as part of the > flow? Seems useful and low impact.
I think it's generally useful and we should do it if there is interest (which seems the case). There's an issue, however, that merits some discussion before proceeding. Some services like https://*.vt.edu/** are so broad that displaying any name and/or description would simply cause confusion. We modified RegisteredServiceImpl such that the description field would allow nulls, and adopted the convention that a null description indicated that the service name and description should not be displayed on the login form. I believe that any general solution needs the capability of opting out of displaying name/description information on the login form. An additional field that makes it explicit would be preferable to our solution. While our convention is suitable for our needs at present, it would likely cause confusion for deployers generally. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
