In practice, the only way to render the user's name alongside the Log Out link is to use the CLogin channel which has another way to retrieve that data. I believe USER_NAME should be set somewhere in the rendering pipeline (perhaps StaticRenderingPipeline.java ?) so the data is available to the main XSL. This will have the side effect of allowing the "welcome" template to operate correctly, too, since it depends on this XSL parameter to show the users's full name.

This missing parameter may be a symptom of a larger problem - I haven't tested them all, but there may be other XSL parameters that could/should be set, too.

Since it works in a vanilla install, I think it's a configuration issue not a code one. So the question is where does the USER_NAME parameter come from? This needs to be documented in the manual once the question is answered.

The vanilla install of uPortal only shows the correct display name in the Log Out section, which is rendered by the CLogin channel, not by the master layout xsl. CLogin knows how to get the display name, but universality.xsl remains ignorant of it.

org.jasig.portal.layout.dlm.providers.ThemeParamInjector injects a variable named "userName" but as pointed out here the XSL uses the value USER_NAME

A quick fix would be to replace the USER_NAME param in universality.xsl with:

<xsl:param name="userName">Guest User</xsl:param>
<xsl:param name="USER_NAME"><xsl:value-of select="$userName"/></xsl:param>