We recently upgraded from 4.1.0.Final to 4.3.0.Final, and have been getting
this exception in various operations:
... 102 more
Caused by: org.postgresql.util.PSQLException: ERROR: column
resourceen0_.uri does not exist
... 120 more
I first encountered this trying to export the configuration
via `keycloak.migration.action=export` , but am now encountering it in a
number of operations such as impersonating a user from the admin console.
We aborted an upgrade to 4.2.1 due to a failed db migration, but 4.3.0
worked fine. Presumably there is a problem with the ddl migration.
Any speculation on root cause and/or a fix? Is there a DDL published
FYI we have keycloak deployed to k8s using an Amazon RDS postgres instance
for the backing store.
Sure, proxy is the obvious name, but for reasons already mentioned by Bruno
it's not really an option for us.
It comes from the Keycloak team, so it should have the Keycloak name in it.
I agree that doesn't automatically state it's a generic OIDC adapter, but
I'd like to keep our name in there.
>From the suggestions so far there are two I like:
* Keycloak Gatekeeper - suggested by Thomas on the poll. I really like this
and it fits nicely with Keycloak. It's also so much cooler than
* Keycloak Standalone Adapter
On Tue, 21 Aug 2018 at 04:27, Fox, Kevin M <Kevin.Fox(a)pnnl.gov> wrote:
> Coming from the outside world, I mostly searched for oidc and proxy as
> thats what I needed. I found oauth2_proxy after a little searching, but
> have been disappointed in how slow its releases are. Bugs aren't getting
> fixed quickly. When I looked at keycloak-proxy initially, I didn't look
> closer for a while as i thought is was keycloak specific.
> So, something like oidc-proxy might get you more successful hits.
> From: keycloak-user-bounces(a)lists.jboss.org [
> keycloak-user-bounces(a)lists.jboss.org] on behalf of Alex Szczuczko [
> Sent: Monday, August 20, 2018 2:04 PM
> To: Bruno Oliveira; Hynek Mlnarik
> Cc: keycloak-dev; keycloak-user
> Subject: Re: [keycloak-user] Keycloak Proxy Rename
> In thinking a new name, I tried to look hard at these things:
> 1. what this software actually does.
> 2. what makes this software desirable to a user.
> 3. what "adapter" has meant for keycloak in the past.
> I'm not the best person to answer these questions, but here's what I've
> dug up:
> 1. Accepts HTTP requests and talks with Keycloak via OIDC to see if
> the client it serves should treat the requests as authenticated
> and/or authorized.
> 2. It avoids the need to install a bit of Keycloak software into the
> users' applications.
> 3. According to the docs: Keycloak client adapters are libraries
> that makes it very easy to secure applications and services with
> Keycloak ... our adapters easy to use and they require less
> boilerplate code than what is typically required by a library.
> #1 is what we've been focusing on with names like "proxy". The reasons
> such names are dissatisfying is there is nothing unique about sitting in
> between two endpoints and doing stuff. So, we need to look at what that
> "stuff" means for Keycloak.
> #3 in combination with #2 tells us what this "stuff" means for Keycloak.
> This new software is clearly not an adapter. Actually, this new software
> accomplishes the mission of an adapter better than adapters themselves!
> Following that logic, Superadapter is my main proposal for a new name.
> Maybe throw in OIDC (oidc-superadapter) if there's ever going to be a
> Alternatively, we could focus on the lack of an adapter, with names
> based on terms like Adapterless:
> - AKI: Adapterless Keycloak Integrator
> - KOSA: Keycloak OIDC Sans-Adapter
> - AKOS: Adapterless Keycloak OIDC Server
> - KOAF: Keycloak OIDC Adapter-Free
> - etc...
> Quoting Bruno Oliveira (2018-08-20 09:54:42)
> > Only to give a brief context for people not aware of it. Keycloak
> > Generic Adapter was not well accepted, because the naming is too
> > vague. So we have to reopen this discussion and think about a better
> > naming.
> > During our team call today I suggested just "keycloak-adapter", which
> > would cover the apps which don't have its own specific adapter
> > solution.
> > That said, maybe we should open a new poll? I just created a new one
> > where people can vote/suggest:
> > https://poll.ly/#/Lbww4ebG
> keycloak-user mailing list
> keycloak-user mailing list
We are considering to transfer or fork the keycloak-proxy to Keycloak
organization. In order to accomplish that, I've been working with Rohith
updating some of its dependencies.
While discussing with our team, we reached the conclusion that call it a
proxy could potentially increase the scope of the project and also give
people the wrong idea. Because would be expected things like load balancing,
rate limiting, and other features. That's not what we want right now.
I would like to gather some feedback from the community before we move forward.
So please vote on the following Doodle:
Also, feel free to suggest other names and it will be included.
 - https://github.com/gambol99/keycloak-proxy
 - https://issues.jboss.org/browse/KEYCLOAK-7265
Before I file a bug, I'd like to discuss one thing.
How's the Default Locale (in realm's theme settings) supposed to work? It
seems to have no effect at all because the realm settings is always
overridden by "Accept-Language" HTTP header that's sent by browser.
Shouldn't have the Default Locale higher priority than the HTTP header?
Keycloak / Red Hat Single Sign-On
Red Hat Czech s.r.o.
Last week Pedro submitted a PR to the Node.js adapter, but the build is
failing because it depends on the changes from Keycloak server master
Today we download the latest stable release from Keycloak to run the
integration tests for this adapter. I would like to change it and follow
the same approach from the Quickstarts, which means clone/build/run
Keycloak server from master. In this way, we can always it test against
the latest changes.
It appears that breaking changes were in the 'latest' version released
about 6 hours ago. Container based on latest image fails with 'hostname not
Using version 4.2.1.final instead of latest, everything works fine.
Note: I am using mssql jdbc driver. This is a working build which only
recently breaks as of the most recent 'latest' update. Prior to that, it
worked fine building off latest, and it works fine now that I have forced
I have a realm with nested groups that denotes a hierarchical corporate
Users belong to one particular group along the /corp/org subtree, but might
also be members of one or more groups from a different subtree, e.g.,
Is it possible to have dedicated admin users at /corp, /branchX, /divisionX
level who can only view and manage the users from their group or subtree
with an admin-console scoped to a fixed realm?
admin-console scoped to group-hierarchy-demo realm:
If a user logs in as divsion1-admin-user, he should only be able to see and
manage the users beneath the path (/corp/org/branch1/division1/*).
Does the fine-grained permission system already support use cases like this?