9:44 a.m.
IMO we should not make KeycloakDS XA by default. Rather, the docs for the
user federation provider should state that if you add another datasource
you need to make that one XA.
1:20 a.m.
Bill - can you comment on this please?
On 13 October 2016 at 15:44, Stian Thorgersen <sthorger(a)redhat.com> wrote:
IMO we should not make KeycloakDS XA by default. Rather, the docs for
the
user federation provider should state that if you add another datasource
you need to make that one XA.
11:31 a.m.
I thought we already agreed we'd make KeycloakDS non-xa?
On 10/17/16 1:20 AM, Stian Thorgersen wrote:
Bill - can you comment on this please?
On 13 October 2016 at 15:44, Stian Thorgersen <sthorger(a)redhat.com
<mailto:sthorger@redhat.com>> wrote:
IMO we should not make KeycloakDS XA by default. Rather, the docs
for the user federation provider should state that if you add
another datasource you need to make that one XA.
11:37 a.m.
Wasn't sure we had, but let's go with that. Thanks
On 17 October 2016 at 17:31, Bill Burke <bburke(a)redhat.com> wrote:
I thought we already agreed we'd make KeycloakDS non-xa?
On 10/17/16 1:20 AM, Stian Thorgersen wrote:
Bill - can you comment on this please?
On 13 October 2016 at 15:44, Stian Thorgersen <sthorger(a)redhat.com> wrote:
> IMO we should not make KeycloakDS XA by default. Rather, the docs for the
> user federation provider should state that if you add another datasource
> you need to make that one XA.
>
2840
days inactive
2844
days old
3 comments
2 participants
participants (2)
-
Bill Burke -
Stian Thorgersen