Describe the bug
Regarding Okta Auth – in the scenario that a user is logged in and is attempting to land on org/repo there is only an empty state instead of including the intended top level banner to require auth. (initially reported by @nicholas-codecov )
To Reproduce
Steps to reproduce the behavior:
Go to a org/repo that has okta enabled
Notice on the org/repo there is no banner (but there is on org)
Expected behavior
When an org is selected no matter what page and IF user is logged in and part of org the empty state should include the login auth (+ top level nav elemetns (org selector, ?, user avatar - should still be visible)
Describe the bug Regarding Okta Auth – in the scenario that a user is logged in and is attempting to land on
org/repo
there is only an empty state instead of including the intended top level banner to require auth. (initially reported by @nicholas-codecov )To Reproduce Steps to reproduce the behavior:
org/repo
that has okta enabledorg/repo
there is no banner (but there is onorg
)Expected behavior When an org is selected no matter what page and IF user is logged in and part of org the empty state should include the login auth (+ top level nav elemetns (org selector, ?, user avatar - should still be visible)