Make JON login look like other Red Hat products. See also JON3-16
Does this bug mean "integrate with keycloak" or is it only about the look&feel?
It is only about Look&Feel *but* since a login redirects to KeyCloak it's the KC login screen that may have to follow the LnF. KeyCloak already defaults to Patternfly/RCUE though but will need some adaptation. If we can't make the KC integration in JON 3.3 we may still need to design the login page following RCUE requirements.
defining the "look like other Red Hat products" more precisely: https://www.patternfly.org/wikis/patterns/user-authentication/loginlogout
associated JIRA on UX side for creating necessary branding elements https://issues.jboss.org/browse/DESIGN-542
Introducing a new web page only for login purposes. (${host}:7080/coregui/login) This had to be done because of the css and javascript separation... there were some collisions between PatternFly and us (jQuery hell in particular and some styles) branch: master link: https://github.com/rhq-project/rhq/commit/8f3d81ddb time: 2014-04-07 20:11:53 +0200 commit: 8f3d81ddbfd4ab8d012668ad7f9dd2a77f221923 author: Jirka Kremser - jkremser message: [BZ 1069667] - (JON3-17) Make JON login look like other Red Hat products - RHQ branding & handling error cases during login process. branch: master link: https://github.com/rhq-project/rhq/commit/b94268811 time: 2014-04-07 20:11:30 +0200 commit: b942688114fb6982058edb2222c40ef5a18f183c author: Jirka Kremser - jkremser message: [BZ 1069667] - (JON3-17) Make JON login look like other Red Hat products - First prototype. Using the PatternFly default logo.
changing the status back to ASSIGNED because it's been done for RHQ, not for JON
cbbca6736 LDAP login/registration support 256895296 CAPS LOCK notification v2 175f76d8c Session expiration 41364182a CAPS LOCK notification v1
Heiko Rupp <hrupp> updated the status of jira JON3-17 to Resolved
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993