5:01 p.m.
This has already been written, but I wanted to start a blank thread so we can discuss
features going into 1.1.
In priority order, the features we'll need for 1.1 seems to be:
* SAML
* OpenID Connect interoperability - test with 3rd party services and client libraries
* Clustering - realm and user cache invalidation + distributed user sessions
* Internationalization support for login and account management
* TOTP improvements - we need a SPI to be able to add more multifactor authentication
mechanisms, as well as support for admins to register totp tokens on behalf of users
(hardware tokens)
5:34 p.m.
I put them in my opinion of priority order
* Clustering
* SAML
* Uberfire Integration (BRMS)
* Fuse FSW
* JIRA Integration (for potential sso.jboss.org deployment).
* SPNEGO Kerberos, so we can integration with OpenIPA (also an
sso.jboss.org deployment requirement too) .
* Open ID Connect interoperability
* Tomcat Adapter
* Jetty Adapter
* Pure servlet adapter
* Node.js Adapter
* Internationalization
* TOTP improvements - we need a SPI to be able to add more multifactor
authentication mechanisms, as well as support for admins to register
totp tokens on behalf of users (hardware tokens)
* IP filtering, fail2ban features.
Clustering is an important deployment issue we have to solve. The rest
are integration requirements we need to solve now so other Red Hat
projects can use Keycloak. Internationalization, TOTP Improvements, and
other new features need to be put off until our integration efforts are
improved.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
5:36 p.m.
Forgot one.
On 9/2/2014 11:34 AM, Bill Burke wrote:
I put them in my opinion of priority order
* Clustering
* SAML
* Uberfire Integration (BRMS)
* Fuse FSW
* JIRA Integration (for potential sso.jboss.org deployment).
* SPNEGO Kerberos, so we can integration with OpenIPA (also an
sso.jboss.org deployment requirement too) .
* Open ID Connect interoperability
* Tomcat Adapter
* Jetty Adapter
* Pure servlet adapter
* Node.js Adapter
* Internationalization
* Improved claim support. Custom claim definition and entry.
* TOTP improvements - we need a SPI to be able to add more
multifactor
authentication mechanisms, as well as support for admins to register
totp tokens on behalf of users (hardware tokens)
* IP filtering, fail2ban features.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
8:39 a.m.
I'm happy with that ordering, although I'd say Open ID Connect interoperability
should be amongst the top 3.
Also, I was wondering if we should base our adapters on existing OAuth2/OpenID Connect
adapters instead of writing them from scratch?
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, 2 September, 2014 5:36:34 PM
Subject: Re: [keycloak-dev] Features for 1.1
Forgot one.
On 9/2/2014 11:34 AM, Bill Burke wrote:
> I put them in my opinion of priority order
>
> * Clustering
> * SAML
> * Uberfire Integration (BRMS)
> * Fuse FSW
> * JIRA Integration (for potential sso.jboss.org deployment).
> * SPNEGO Kerberos, so we can integration with OpenIPA (also an
> sso.jboss.org deployment requirement too) .
> * Open ID Connect interoperability
> * Tomcat Adapter
> * Jetty Adapter
> * Pure servlet adapter
> * Node.js Adapter
> * Internationalization
* Improved claim support. Custom claim definition and entry.
> * TOTP improvements - we need a SPI to be able to add more multifactor
> authentication mechanisms, as well as support for admins to register
> totp tokens on behalf of users (hardware tokens)
> * IP filtering, fail2ban features.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
10:11 a.m.
What would be your time frame for 1.1?
W dniu 03/09/14 08:39, Stian Thorgersen pisze:
I'm happy with that ordering, although I'd say Open ID
Connect
interoperability should be amongst the top 3.
Also, I was wondering if we should base our adapters on existing
OAuth2/OpenID Connect adapters instead of writing them from scratch?
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com> To:
> keycloak-dev(a)lists.jboss.org Sent: Tuesday, 2 September, 2014
> 5:36:34 PM Subject: Re: [keycloak-dev] Features for 1.1
>
> Forgot one.
>
> On 9/2/2014 11:34 AM, Bill Burke wrote:
>> I put them in my opinion of priority order
>>
>> * Clustering * SAML * Uberfire Integration (BRMS) * Fuse FSW *
>> JIRA Integration (for potential sso.jboss.org deployment). *
>> SPNEGO Kerberos, so we can integration with OpenIPA (also an
>> sso.jboss.org deployment requirement too) . * Open ID Connect
>> interoperability * Tomcat Adapter * Jetty Adapter * Pure servlet
>> adapter * Node.js Adapter * Internationalization
>
> * Improved claim support. Custom claim definition and entry.
>
>> * TOTP improvements - we need a SPI to be able to add more
>> multifactor authentication mechanisms, as well as support for
>> admins to register totp tokens on behalf of users (hardware
>> tokens) * IP filtering, fail2ban features.
>
>
> -- Bill Burke JBoss, a division of Red Hat
> http://bill.burkecentral.com
> _______________________________________________ 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
--
Bolesław Dawidowicz
JBoss Portal Platform Architect | GateIn Portal Project Lead
2:30 p.m.
Plan is to have a release every time we implement something major.
On 9/3/2014 4:11 AM, Bolesław Dawidowicz wrote:
What would be your time frame for 1.1?
W dniu 03/09/14 08:39, Stian Thorgersen pisze:
> I'm happy with that ordering, although I'd say Open ID Connect
> interoperability should be amongst the top 3.
>
> Also, I was wondering if we should base our adapters on existing
> OAuth2/OpenID Connect adapters instead of writing them from scratch?
>
> ----- Original Message -----
>> From: "Bill Burke" <bburke(a)redhat.com> To:
>> keycloak-dev(a)lists.jboss.org Sent: Tuesday, 2 September, 2014
>> 5:36:34 PM Subject: Re: [keycloak-dev] Features for 1.1
>>
>> Forgot one.
>>
>> On 9/2/2014 11:34 AM, Bill Burke wrote:
>>> I put them in my opinion of priority order
>>>
>>> * Clustering * SAML * Uberfire Integration (BRMS) * Fuse FSW *
>>> JIRA Integration (for potential sso.jboss.org deployment). *
>>> SPNEGO Kerberos, so we can integration with OpenIPA (also an
>>> sso.jboss.org deployment requirement too) . * Open ID Connect
>>> interoperability * Tomcat Adapter * Jetty Adapter * Pure servlet
>>> adapter * Node.js Adapter * Internationalization
>>
>> * Improved claim support. Custom claim definition and entry.
>>
>>> * TOTP improvements - we need a SPI to be able to add more
>>> multifactor authentication mechanisms, as well as support for
>>> admins to register totp tokens on behalf of users (hardware
>>> tokens) * IP filtering, fail2ban features.
>>
>>
>> -- Bill Burke JBoss, a division of Red Hat
>> http://bill.burkecentral.com
>> _______________________________________________ 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
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
2:39 p.m.
It is a long list. So in practice it could feed 1.1 and 1.2 at least right?
I like time boxed approach.
On 09/03/2014 02:30 PM, Bill Burke wrote:
Plan is to have a release every time we implement something major.
On 9/3/2014 4:11 AM, Bolesław Dawidowicz wrote:
> What would be your time frame for 1.1?
>
> W dniu 03/09/14 08:39, Stian Thorgersen pisze:
>> I'm happy with that ordering, although I'd say Open ID Connect
>> interoperability should be amongst the top 3.
>>
>> Also, I was wondering if we should base our adapters on existing
>> OAuth2/OpenID Connect adapters instead of writing them from scratch?
>>
>> ----- Original Message -----
>>> From: "Bill Burke" <bburke(a)redhat.com> To:
>>> keycloak-dev(a)lists.jboss.org Sent: Tuesday, 2 September, 2014
>>> 5:36:34 PM Subject: Re: [keycloak-dev] Features for 1.1
>>>
>>> Forgot one.
>>>
>>> On 9/2/2014 11:34 AM, Bill Burke wrote:
>>>> I put them in my opinion of priority order
>>>>
>>>> * Clustering * SAML * Uberfire Integration (BRMS) * Fuse FSW *
>>>> JIRA Integration (for potential sso.jboss.org deployment). *
>>>> SPNEGO Kerberos, so we can integration with OpenIPA (also an
>>>> sso.jboss.org deployment requirement too) . * Open ID Connect
>>>> interoperability * Tomcat Adapter * Jetty Adapter * Pure servlet
>>>> adapter * Node.js Adapter * Internationalization
>>>
>>> * Improved claim support. Custom claim definition and entry.
>>>
>>>> * TOTP improvements - we need a SPI to be able to add more
>>>> multifactor authentication mechanisms, as well as support for
>>>> admins to register totp tokens on behalf of users (hardware
>>>> tokens) * IP filtering, fail2ban features.
>>>
>>>
>>> -- Bill Burke JBoss, a division of Red Hat
>>> http://bill.burkecentral.com
>>> _______________________________________________ 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
>>
>
>
>
--
Bolesław Dawidowicz
JBoss Portal Platform Architect | GateIn Portal Project Lead
2:25 p.m.
On 9/3/2014 2:39 AM, Stian Thorgersen wrote:
I'm happy with that ordering, although I'd say Open ID
Connect interoperability should be amongst the top 3.
Also, I was wondering if we should base our adapters on existing OAuth2/OpenID Connect
adapters instead of writing them from scratch?
We could possibly ditch our non-integrated adapter, but our integrated
adapters (wildfly, jboss) are designed to fit into a security
framework/SPI and it wouldn't be feasible to use an existing third-party
adapter to implement them.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
1:47 p.m.
On Tuesday, September 2, 2014, Bill Burke <bburke(a)redhat.com> wrote:
I put them in my opinion of priority order
* Clustering
* SAML
* Uberfire Integration (BRMS)
* Fuse FSW
* JIRA Integration (for potential sso.jboss.org deployment).
* SPNEGO Kerberos, so we can integration with OpenIPA (also an
sso.jboss.org deployment requirement too) .
* Open ID Connect interoperability
* Tomcat Adapter
Isn't there already a Tomcat(7?) Adapter?
* Jetty Adapter
* Pure servlet adapter
* Node.js Adapter
* Internationalization
* TOTP improvements - we need a SPI to be able to add more multifactor
authentication mechanisms, as well as support for admins to register
totp tokens on behalf of users (hardware tokens)
* IP filtering, fail2ban features.
Clustering is an important deployment issue we have to solve. The rest
are integration requirements we need to solve now so other Red Hat
projects can use Keycloak. Internationalization, TOTP Improvements, and
other new features need to be put off until our integration efforts are
improved.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org <javascript:;>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Sent from Gmail Mobile
2:31 p.m.
On 9/3/2014 7:47 AM, Matthias Wessendorf wrote:
Isn't there already a Tomcat(7?) Adapter?
Work has been started on it and it would be easy to add it as the code
would be almost the same as the EAP 6.x adapter.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
3522
days inactive
3523
days old
9 comments
4 participants
participants (4)
-
Bill Burke -
Bolesław Dawidowicz -
Matthias Wessendorf -
Stian Thorgersen