Certificate Authentication
by Alarik Myrin
I noticed that Certificate Authentication was not on the list for 1.1 --
any idea when that might get added?
Alarik
12 years
ugh, google changed again
by Bill Burke
FYI:
You now have to specify a project name and an email on the consent page
in the GOogle Console, otherwise you get a login error.
I need to update our documentation.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
12 years
Features for 1.1
by Stian Thorgersen
This has already been written, but I wanted to start a blank thread so we can discuss features going into 1.1.
In priority order, the features we'll need for 1.1 seems to be:
* SAML
* OpenID Connect interoperability - test with 3rd party services and client libraries
* Clustering - realm and user cache invalidation + distributed user sessions
* Internationalization support for login and account management
* TOTP improvements - we need a SPI to be able to add more multifactor authentication mechanisms, as well as support for admins to register totp tokens on behalf of users (hardware tokens)
12 years
Examples overview README.md
by Stian Thorgersen
I've added 'examples/README.md' with a brief overview over all the examples. This replaces 'examples/demo-template/README.md.overview', which only mentioned the demo.
Now I'll add instructions to 'unconfigured-demo/README.md' on how to configure it with an existing Keycloak server. I'll make sure the instructions work with either a local or external server. It would be good if the screencast follows the same order as this README.md so they can be used together.
12 years
AccoutTest.viewLog randomly fails
by Bill Burke
AccountTest.viewLog:403 expected:<[login]> but was:<[register]>
This happens to me a lot and I can't figure out why. It only happens in
a full build. I can't replicate it in IDE, or if I run testsuite alone.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
12 years
PicketLink and KeyCloak Integration
by Pedro Igor Silva
Hey Guys,
I've mentioned in a previous thread the work we are doing in PicketLink to support different token formats. One of the use cases we're considering is about consuming KeyCloak tokens.
PicketLink is now able to consume tokens from KeyCloak in order to perform security checks. This is a very important step in order to combine all the functionalty provided by KeyCloak and PicketLink in a single application. With a minimal configuration and effort.
From our last discussion, Bill said that we can have the integration code into the KeyCloak repository. If this is still true, I would like to start to prepare a PR to send all the code we need for this integration. The code is very simple and requires the usage of the KeyCloak API in order to properly parse tokens and information from them. Here is an example:
https://github.com/pedroigor/jboss-wfk-quickstarts/tree/token-store-witho...
The good news is that people is already asking for this :)
Wdyt ?
Regards.
Pedro Igor
12 years
prep for 1.0.Final
by Bill Burke
Please no more UI changes or distribution directory structure changes.
I am re-doing screencasts and don't want these screencasts to be
obsolete as soon as we do them.
We should shy away from API or DB schema changes. It would be cool if
documentation could be reviewed/expanded/improved while we wait to see
if any bugs filter in from RC.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
12 years
