Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Description
In Bitbucket, the requirement is to get an option to login to Bitbucket when Basic Authentication is disabled (both UI and REST API) and the system admin user is not handy.
Currently, we can use lockout_recovery and auth_fallback features for any kind of login issue when Basic Authentication is disabled in UI and SAML is enabled. But if a user does not have a system admin user available in their system (configured on LDAP) and Basic Authentication is disabled ("Username and password" on login windows as well as "Allow basic authentication on API calls", we don't get any option to login to Bitbucket even with lockout_recovery and auth_fallback features.
To avoid this stopper, the database table needs to be updated which is not the correct option to resolve this issue.
I have tried to cover most of the scenarios in the following article and Use Case2 is the place where concern is raised through this ticket.
https://confluence.atlassian.com/pages/viewpage.action?pageId=1369442206&permissionViolation=true&permissionViolation=true
Please have a look and share your input.