[keycloak-user] kcinit status

[Stian Thorgersen]

It's not a priority due to it not being a useful tool, but rather other
higher priority tasks.

The engineer that developed the kcinit prototype has left the team and we
are now in a situation where no one knows it well. Further, there are
design issues in it that I'm not convinced about.

For it to become a supported tool there are at least a few things that
needs to be done:

* Remove Java based testing from keycloak/keycloak and add testing to Go
repo itself. As well as review test coverage
* Review design and consider if anything needs to change
  - Storage of tokens
  - How its used by multiple clients. I'm far from keen on it using token
exchange as it does today
* Review and resolve outstanding bugs
* Review code
* Documentation

Contributions would be more than welcome. Bug fixes including tests are
obvious candidates, design/functionality changes should be discussed on the
dev mailing list first ideally.


On Wed, 2 Jan 2019 at 18:19, Fox, Kevin M <Kevin.Fox at pnnl.gov> wrote:

> Yes I filed jira tickets. they have been sitting around for a while.
>
> kcinit does seem quite important if you want to use keycloak for
> kubernetes authentication and want to support the command line. It is
> troubling to hear it is not going to be a focus for a year. Maybe its
> because openshift would use it in a slightly different way then vanilla k8s
> would. But since keycloak is trying to become part of the cncf, that would
> be an important thing to support I think. I am trying to use keycloak with
> a vanilla kubernetes and support both the cli and the web ui securely.
>
> I might be willing to contribute to it too if that would help move things
> along. Its been unclear though that such contributions would be welcome?
>
> Thanks,
> Kevin
>
> ------------------------------
> *From:* Stian Thorgersen [sthorger at redhat.com]
> *Sent:* Wednesday, January 02, 2019 6:18 AM
> *To:* Bruno Oliveira
> *Cc:* Fox, Kevin M; keycloak-user at lists.jboss.org
> *Subject:* Re: [keycloak-user] kcinit status
>
> kcinit is in a prototype stage and is not released or documented as it's
> not ready for use. From our priorities lists it's doubtful that much will
> happen with this tool this year.
>
> On Wed, 2 Jan 2019 at 14:41, Bruno Oliveira <bruno at abstractj.org> wrote:
>
>> Hi Kevin, did you file Jiras for the bugs you mentioned? If not please
>> do, and also make sure to add all the details needed to reproduce the
>> issue.
>>
>>
>> On 2018-12-21, Fox, Kevin M wrote:
>> > Not much has happened with kcinit in a long time and it has a few
>> outstanding bugs in the way of working for us. What is the status of the
>> project?
>> >
>> > Thanks,
>> > Kevin
>> > _______________________________________________
>> > keycloak-user mailing list
>> > keycloak-user at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/keycloak-user
>>
>> --
>>
>> abstractj
>> _______________________________________________
>> keycloak-user mailing list
>> keycloak-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-user
>>
>