Based on discussion on Stian, let me reopen this topic and add a suggestion.
How about "Standalone Keycloak Adapter" or just "Standalone Adapter"?
On Mon, Jun 25, 2018 at 5:44 PM Bruno Oliveira <bruno(a)abstractj.org> wrote:
Good afternoon,
We are considering to transfer or fork the keycloak-proxy[1] to Keycloak
organization. In order to accomplish that, I've been working with Rohith
updating some of its dependencies[2].
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:
https://doodle.com/poll/gux626ktscgpr96t
Also, feel free to suggest other names and it will be included.
[1] -
https://github.com/gambol99/keycloak-proxy
[2] -
https://issues.jboss.org/browse/KEYCLOAK-7265
--
abstractj
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user