Keycloak.org
by Gabriel Cardoso
I did a proposal to just update the header of Keycloak.org
Bill, can you give me access to the site so I can update it?
Gabriel
---
Gabriel Cardoso
User Experience Designer @ Red Hat
10 years, 3 months
demo-template
by Bill Burke
I removed all the examples/*-demo projecst and consolidated it into one
project examples/demo-template. The distribution/examples-dist project
sorts things out and creates 3 different copies in the example
distribution with config files according to wildfy, as7, and a 3rd one,
an unconfigured project (for screencast tutorial).
So, to run the demo now, you have have to create the distro for examples.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10 years, 3 months
Move instructions to configure social providers into documentation
by Stian Thorgersen
Currently when adding a social provider there's a link (?) that opens a modal panel with instructions on how to configure the app with the social provider itself. For example when adding Google there's some instructions on how to create the application and what key/secrets should be added in the admin console.
Recently both Google and Facebook have changed their console making the way these are configured quite different. To update the instructions we're then required to update the admin console. As I see it there's two options:
a) Remove this feature and the required instructions to the Keycloak documentation - this is my prefer option
b) Make the social provider itself provide the instructions as a html snippet - this makes it possible to update the social provider jar and nothing else (for example keycloak-social-google.jar)
Thoughts?
10 years, 3 months
PRs allowed still, but...
by Bill Burke
If you want to send PRs please do, but PLEASE PLEASE check you don't
break anything. And do not do anything that will effect documentation.
Definitely doing a release Thursday 23rd. As long as things work, that
date is unmovable. Whatever doco we have then is what we'll have.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10 years, 3 months
removed cookieLoginAllowed
by Bill Burke
I removed this switch. It originally would set a identity cookie for
the auth-server's domain/path if "true". You can't really have SSO
without it, so, I just removed it. If somebody asks for the feature,
we'll put it back in.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10 years, 3 months
url changes in
by Bill Burke
realms, apps, and roles use names instead of ids now for admin ui and
token service (where applicable). Still need to do for oauth-clients,
but I'll save that for next release.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10 years, 3 months
phase1 of url changes
by Bill Burke
Everything now uses. I NEED PLEASE TO TEST EVERYTHING! Something may
have fell through the cracks.
/auth/rest/admin/realms/{realm-name}
/auth/rest/realms/{realm-name}/tokens
...
Details:
* This change was a BITCH! 64 files changed.
* ID *must* still be used in the data model for db secondary keys and
constraints.
* Realm names are still mutable and changeable.
Phase 2 will be:
* Remove code-url and auth-url from adapter config and just go with
"keycloak-url". This will be the base URL of the server.
* Use application name instead of ID in application urls.
Any other URL changes?
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10 years, 3 months
next release: refactoring
by Bill Burke
After Alpha 1, I'd like to focus on refactoring and improving the
overall code quality. For example, it has been brutally painful to
change URI schemes from /auth-server to /auth and also using Realm name
instead of id to generate URLs. This is a problem in both the admin
console and services. I'm sure there's other areas too.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10 years, 3 months
Token scope
by Stian Thorgersen
Could we use the standard scope attribute from JWT instead of the custom realm_access and resource_access?
An example scope could be:
{
"scope": "realm-role,app-1/app-role-1,app-2/app-role-2"
}
10 years, 3 months
