Invalid user or password or the account is blocked due to multiple failed login attempts - authentication

Error Message:- Invalid user or password or the account is blocked due to multiple failed login attempts. If so, it will be unblocked automatically in a short time.
I have installed Openproject in Ubuntu environment.
Today morning i updated the Openproject.
When i tried to login using my user name and password I got the above error message
The database is Postgresql.
I could able to login to db.
what is the solution to resolve this issue and i am want to unblock the account.
All the accounts, including admin account could not able to login.

Create a new username and password with admin rights in postgresql DB.
Grant admin rights to the user.
Login to the website using the new username and password.
GO to adminstration - Authentication -
check
AUTOMATED USER BLOCKING
Block user after this number of failed login attempts
--Give the input Zero - 0
It will allow the user to login any number of times if they fail.
thanks

Related

Opencard admin is logging in to same account for different profiles

I am building an opencart 3.0.3.8 site. I have a problem with admin login. I have created 2 admin profiles say User 1 and User 2. The problem is its getting logged in to the User 1 account even if I logged in using user 2 credentials. I don't know if its a bug or some misconfiguration from my side. Requesting your inputs on possible ways to fix this.
I tried deleting the user 1 profile from db directly and it completely disabled admin login.
I can login using the User 1 credentials even if all users are disabled.

Invalid Login Credentials in Oracle APEX After Resetting the Password from the Administration Panel in ADB-S

I reset one of my administrator user's passwords using the APEX Administration Interface and now he can't login into the workspace, I already tried to reset his password several times with passwords that comply with ADB-S' (Autonomous Database Shared's) Complexity rules but APEX is still throwing an "Invalid Login Credentials" error as if the password, workspace or account name are incorrect. I already reviewed that the three details are to-the-letter, but the error is still showing up
It took me about 1 hour to figure it out but here's what happens:
Turns out that when an APEX workspace is created, the administrative account is linked with a Database Schema, just as it happens in a normal installation BUT the catch is that APEX Login UI in ADB-S uses "Database Credentials" to login, and if both passwords don't match, the UI will deny the login with the "Invalid credentials error".
The solution to this issue is to change the password using the APEX UI and then change the associated schema password to be the same as the one you entered in the APEX UI, once that's done, in that order, you'll be able to login with your administrator user again.

Microsoft graph is remembering the user after authentication

I'm using Microsoft graph in my Android project to authenticate users.
I'm doing so via this method:
https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-v1-android
after a successful login Microsoft remembers the user email, so next time when user is trying to login it will suggest to use a previously logged in account. If user chooses a previously used email, a password is not required.
Problem raises when we have a single device where multiple users need to login via Microsoft. In this case new user will see the email of previously logged users and can select their email and log into account without entering any password.
My question is how can I avoid this behavior and close the session after each login?
Thank you!
You can tell ADAL to request credentials again by switching PromptBehavior from Auto to Always:
// Perform authentication requests
mAuthContext.acquireToken(
getActivity(),
RESOURCE_ID,
CLIENT_ID,
REDIRECT_URI,
PromptBehavior.Always,
getAuthInteractiveCallback());

(Mac) Realm Object Server Login Failed: Email/Password Incorrect

I installed Realm on computer1 and ran the Realm Object Server (creating a new admin user) then installed and ran Realm Object Server on computer2 attempting to create the same admin user I created on computer1. It immediately went to the login page where I assumed it had recognized my credentials from computer1 so I then filled in the same credentials and tapped Login. For some reason this alert is now showing on the screen:
Login Failed: Email/Password combination incorrect.
In the server logs it states:
warn: auth.password: Handle request failed with: InvalidCredentials: The provided credentials are invalid.: Given account: foo#bar.com
I then restarted the Realm Server and attempted to create a different admin user with different credentials, after filling in the credentials and tap "submit" I am immediately taken to the login page where it gives the alert now saying:
An error occured while setting up your account.
What is also interesting, is that after trying to create that new account I don't receive any information in the logs after tapping submit.
It's not possible to run two copies of the Realm Object Server on multiple computers and share user accounts between them at the moment. Those will be two wholly separate and independent copies of the Realm Object Server.
Unless you registered two separate copies of the same admin account, the second login attempt will fail because the account doesn't exist in that instance.
We're working on adding additional scaling capabilities to the Realm Mobile Platform. Thanks for filing an issue on the Mobile Platform GitHub; we'll take it into consideration.

OPenLDAP account lockout

I have openldap server and lot of applications are getting authentication setup via LDAP. I am using an Auth user for the apps which is getting locked again and again because of that I have to reset the password of Auth user to make my application start authentication again.
I have implemented ppolicy and made and exception for my Auth user. Which seems working for sometime but account locking started again. I have account lockout policy for 5 wrong password attempts which is working fine with exception to Auth user when I try manually entering wrong password more than 5 times.. So I am suspecting there must be some other system policy for account lockup may be for 250+ wrong attempts or so...
I am just looking for an option to make Auth user unlimited wrong password tries. Is it possible? Is yes how?