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

UDUF (U4-10975) Failed Logon Attempts resets to 0 after maximum number of attempts #2462

Merged
merged 1 commit into from
Jul 14, 2018

Conversation

iofsauron
Copy link

Failed Logon Attempts resets to 0 after maximum number of attempts

See this: http://issues.umbraco.org/issue/U4-10975

@Shazwazza Shazwazza changed the title Failed Logon Attempts resets to 0 after maximum number of attempts UDUF (U4-10975) Failed Logon Attempts resets to 0 after maximum number of attempts Feb 26, 2018
@nul800sebastiaan nul800sebastiaan changed the base branch from dev-v7.8 to dev-v7 February 27, 2018 10:48
@poornimanayar
Copy link
Contributor

Hi @iofsauron ,

Many thanks for the PR. I am going to review this and I shall keep you posted on how things go this end with the testing and reviewing. :-)

Regards,
Poornima, Community Pull Request team

@@ -507,15 +507,22 @@ private static string NewSecurityStamp()

#endregion

public override Task<IdentityResult> SetLockoutEndDateAsync(int userId, DateTimeOffset lockoutEnd)
public override async Task<IdentityResult> SetLockoutEndDateAsync(int userId, DateTimeOffset lockoutEnd)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately this is a public method in a public class. Changing the method is a breaking changes as it will require everyone using it to have to recompile the code.
So we'll have to keep this one non-async for now!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can change to async, this isn't changing the method signature at all. It's already async enabled since its returning a Task. Same as the other method. All the async keyword does is modify the IL used to call the method.

/// <remarks>
/// Doesnt set fail attempts back to 0
/// </remarks>
public override async Task<IdentityResult> AccessFailedAsync(int userId)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for this method, unfortunately we can't just change it to async.

@nul800sebastiaan nul800sebastiaan merged commit c2039ef into umbraco:dev-v7 Jul 14, 2018
@nul800sebastiaan
Copy link
Member

Thanks @iofsauron! Sorry for the late reply but we finally got round to trying this out and it works great! 👍 🏅

If you have a profile on Our Umbraco, could you link it here? I'd love to give you a contributor badge!

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

Successfully merging this pull request may close these issues.

4 participants