mdui:Description from metadata not showing up on Shibboleth 3.3 login page

[Cantor, Scott]

On 2/8/17, 1:29 PM, "users on behalf of Matthew Brookover" <users-bounces at shibboleth.net on behalf of mbrookov at mines.edu> wrote:

>    First off, I decided to start with a fresh install of Shibboleth 3.3.  I did not do a full production ready configuration, just
> enough for InCommon, ldap, kerberos, etc.  My hope was the problem would just go away.  Unfortunately,
> rpUIContext.getLogo() and rpUIContext.getServiceDescription() are still not populated in login.vm.

A regression I could easily understand from my refactoring, but I don't know why the Eclipse results would be any different than a new install, they should be largely the same. Unclear.

> I noticed that rpUIContext does work in intercept/attribute-release.vm, it calls getLogo and displays it on the consent
> page.

That should get me enough to track down what broke and the fix will probably involve a simple patch to a flow definition once you file the bug and we track it down.
    
> Both appear to be pulling from net.shibboleth.idp.ui.context.RelyingPartyUIContext.  Not sure what 
> opensamlProfileRequestContext.getSubcontext does that is different from authenticationContext.getSubcontext.

It's a tree, this is about positioning of nodes and something getting moved without making a corresponding change that needed to happen to account for it.

-- Scott