You can still be logged in to sso.jboss.org but not logged in to community.jboss.org. This produces a very odd user experience, where you can be logged in to some systems, but not others. This is especially apparent with REST calls to community.jboss.org, as the REST call to sso.jboss.org tells us that the user is logged in (so we show the user is logged in), but the REST call to community.jboss.org returns a 403. It's very counterintuitive to realise you have to then visit community.jboss.org to get your login restored.

I guess that the login check on jive relies on some session, and doesn't check sso.jboss.org to gain the authoritative state of login.