-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
I've just sent a PR for console that enables the Keycloak integration.
What does this mean for you, as a developer?
- - When opening the console, you'll be presented with the login page
provided by Keycloak. If it's the first time you are opening after
building the kettle, you'll need to register an account. After that,
you'll be redirected back to the console. On the subsequent runs,
you'll just need to login again, as long as the data directory is
preserved (ie: until you rebuild kettle)
- - Running your UI plugin via ui-components with "connect-COMPONENT" is
*not* affected.
- - Your WAR deployment is not protected, meaning, you can still call
your backend without passing any credentials.
Note that the UI integration is temporary, as hawt.io will provide a
better Keycloak integration "natively".
- - Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJU/wpKAAoJECKM1e+fkPrXKkUH/RDGtIIfTqxyVBxNhXfQcnzr
jpA2nRLTp56eMZYP43d2Om13lbDYtAguiUPP2k5Y3huDAYQLQLAVHbF9hRenaiie
actkuiEZ60rxZ+qYUMt/EjBpPdFupHnRra3Uc/G5LMAWOh1eSEjmrBM4bShSgj3M
CSmtrTcXuK+QdFJ7OkzA4BoX+uK5z/EX2iNsYRITAI1281xG1zK3ndAt6HQwKCvs
DDJauCw/DVdOiucJzXrfzFx4CwecjyK9lJUNRvCkyO4qtukH+i/LP09nnt+RC2Di
+fyeDhEzQrLIQTpk8vpbCe4aRKZvLP25AVCgVnh0017aUMgtMO2neOleM/4weWg=
=38rr
-----END PGP SIGNATURE-----