Sorry, I may have confused myself. I thought
browse/KEYCLOAK-5209 was already available at 3.2.1. I guess it's the same
bug, I just didn't realize where it occurred.
Best regards,
Thiago
On Mon, Jul 31, 2017 at 9:20 AM, Thiago Presa <thiago.addevico(a)gmail.com>
wrote:
Sure. It seems that what was fixed was the e-mail verification
timeout,
which renders the theme template email-verification.ftl.
What I'm reporting now is that when the user attempts to perform a social
login, an e-mail is sent to his e-mail address, asking for confirmation of
the account link. This e-mail renders the template
identity-provider-link.ftl This now is rendering the Default
Admin-Initiated Action Lifespan.
Best regards,
Thiago
On Mon, Jul 31, 2017 at 2:43 AM, Hynek Mlnarik <hmlnarik(a)redhat.com>
wrote:
> I don't think I can confirm it anymore. Can you please explain how
> that differs from case "when the user tries to federate with google"
> that you reported originally and that has been fixed in latest master
> at that time?
>
> --Hynek
>
> On Fri, Jul 28, 2017 at 7:43 PM, Thiago Presa <thiago.addevico(a)gmail.com>
> wrote:
> > Hi,
> >
> > It seems that there is an issue analogous to
> >
https://issues.jboss.org/browse/KEYCLOAK-5209 but regarding account
> link.
> > Can somebody confirm this?
> >
> > Best regards,
> > Thiago
> >
> > On Thu, Jul 20, 2017 at 4:29 PM, Thiago Presa <
> thiago.addevico(a)gmail.com>
> > wrote:
> >>
> >> Hi,
> >>
> >> Another change that I've noticed from 3.1.0.Final to 3.2.0.Final is
> that
> >> the email "Test connection" button now fails with the message
"Error!
> Logged
> >> in user does not have an e-mail.". The email validation, however,
keeps
> >> working just fine. Is this working as intended?
> >>
> >> Best regards,
> >> Thiago
> >>
> >> On Wed, Jul 19, 2017 at 10:25 AM, Hynek Mlnarik <hmlnarik(a)redhat.com>
> >> wrote:
> >>>
> >>> Yes, thank you.
> >>>
> >>>
https://issues.jboss.org/browse/KEYCLOAK-5209
> >>>
> >>> --Hynek
> >>>
> >>> On Wed, Jul 19, 2017 at 2:48 PM, Thiago Presa <
> thiago.addevico(a)gmail.com>
> >>> wrote:
> >>> > Sure. We've tested the login registration itself and the
timeout is
> in
> >>> > fact
> >>> > correct. However, when the user tries to federate with google (and
> >>> > Keycloak
> >>> > tries to verify that e-mail) the timeout is 12 hours. Can you
> confirm
> >>> > that?
> >>> >
> >>> > Best regards,
> >>> > Thiago Presa
> >>> >
> >>> > On Wed, Jul 19, 2017 at 2:30 AM, Hynek Mlnarik
<hmlnarik(a)redhat.com
> >
> >>> > wrote:
> >>> >>
> >>> >> I've checked email verification upon user registration -
the
> timeout
> >>> >> in the e-mail is 5 minutes as expected. Can you share more
details
> of
> >>> >> your setup?
> >>> >>
> >>> >> --Hynek
> >>> >>
> >>> >> On Tue, Jul 18, 2017 at 7:27 PM, Thiago Presa
> >>> >> <thiago.addevico(a)gmail.com>
> >>> >> wrote:
> >>> >> > Hi,
> >>> >> >
> >>> >> > We've noticed a change between 3.1.0.Final and
3.2.0.Final that
> >>> >> > we're
> >>> >> > not
> >>> >> > sure is intentional. The e-mail verification time changed
from 5
> >>> >> > minutes
> >>> >> > (User-Initiated Action Lifespan) to 12 hours (Default
> >>> >> > Admin-Initiated
> >>> >> > Action Lifespan). It seems weird for us because it does
not seem
> >>> >> > admin-initiated, since it is part of the default user
> registration
> >>> >> > process
> >>> >> > to verify his or her email. Is this a bug?
> >>> >> >
> >>> >> > Best regards,
> >>> >> > Thiago Presa
> >>> >> > _______________________________________________
> >>> >> > keycloak-user mailing list
> >>> >> > keycloak-user(a)lists.jboss.org
> >>> >> >
https://lists.jboss.org/mailman/listinfo/keycloak-user
> >>> >>
> >>> >>
> >>> >>
> >>> >> --
> >>> >>
> >>> >> --Hynek
> >>> >
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> --Hynek
> >>
> >>
> >
>
>
>
> --
>
> --Hynek
>