+1 from dev perspective. I believe it is worth checking with keycloak-user
as well.
I guess deprecation period would be needed. IIRC, this was added with OSIN
replacement in mind [1]. Is this plan obsoleted?
[1]
https://github.com/keycloak/openshift-integration/blob/master/README.md
On Wed, Sep 18, 2019 at 2:30 PM Marek Posolda <mposolda(a)redhat.com> wrote:
+1
Do we have a chance to do it now or is some "deprecation period" needed?
It may help to save some work with refactoring of authentication flows,
which will be required for multi-token and step-up authentication support.
Marek
On 06. 09. 19 11:54, Bruno Oliveira wrote:
> +1
>
> On Fri, Sep 6, 2019 at 6:48 AM Stian Thorgersen <sthorger(a)redhat.com>
wrote:
>> kcinit and it's associated text-based authentication flows adds quite a
bit
>> of complexity. It was never fully completed and we don't have capacity
to
>> complete it.
>>
>> Text-based authentication flows are also not really all that useful.
There
>> are other better approaches to authenticate devices without a web
browser,
>> and when there is a web browser that should be used rather than cli.
>>
>> I propose we remove both kcinit as well as the text-based authentication
>> flows. We also need to revert KeycloakInstalled to how it was prior to
this
>> was added as it is currently fairly broken.
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev