Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect time shift for LockoutEndDateUtc #21

Closed
Niklas-Peter opened this issue Jun 29, 2017 · 3 comments
Closed

Incorrect time shift for LockoutEndDateUtc #21

Niklas-Peter opened this issue Jun 29, 2017 · 3 comments
Assignees
Labels

Comments

@Niklas-Peter
Copy link

My local time (Germany) is UTC+2.

I set
options.Lockout.DefaultLockoutTimeSpan = TimeSpan.FromHours(4);

and forced the lockout at 7.30 (UTC). However, in the database 9.30 is saved instead of the expected result 11.30. I think it is caused by your time conversions. Using the EntityFramework ASP.NET Identity storage it works as expected.

@dlmelendez
Copy link
Owner

@Niklas-Peter Thanks for reporting this. Yes, it looks like this logic was moved from the EF store into the UserManager at some point. Which package (aspnet or aspnetcore) are you using and what version?
Thanks,
Dave

@Niklas-Peter
Copy link
Author

The current version for ASP.NET core: ElCamino.AspNetCore.Identity.AzureTable 1.6.6

@dlmelendez
Copy link
Owner

@Niklas-Peter Fixed in release 1.6.7. Thanks, Dave

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants