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

Unable to view Okta login link if incorrect credentials entered #10337

Closed
TnTBass opened this issue Sep 12, 2022 · 0 comments
Closed

Unable to view Okta login link if incorrect credentials entered #10337

TnTBass opened this issue Sep 12, 2022 · 0 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@TnTBass
Copy link

TnTBass commented Sep 12, 2022

NetBox version

v3.2.9

Python version

3.10

Steps to Reproduce

  1. Enable Okta integration
  2. Attempt to log into Netbox using non Okta credentials that do not work (eg: Not a local account)

Expected Behavior

Error message should not cover Okta link, or disappear automatically.

Ideally, Okta login would be more prevalent if Okta integration was enabled, hiding (but not eliminating) 'normal' authentication method in case local login is required.

Observed Behavior

Error message gets created "Please enter a correct username and password. Note that both fields may be case-sensitive." covering up the Okta link. User is unable to log in with Okta unless navigating back to Netbox URL to remove the error.

No indication to the user that Okta should be used, and after the error message occurs, it hides that Okta is enabled.

@TnTBass TnTBass added the type: bug A confirmed report of unexpected behavior in the application label Sep 12, 2022
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Sep 15, 2022
@jeremystretch jeremystretch self-assigned this Sep 15, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants