Each step of signing in or out adds a history entry:
startAuthFlow (src/services/auth/oauth.ts:202) goes to the server's sign-in page with window.location.href
endSession (src/services/auth/session.ts) defaults to window.location.href
signOut (src/services/auth/signOut.ts) uses window.location.href for the end-session URL and navigate('/login')
Fix: location.replace in those three places and navigate('/login', { replace: true }); and when LoginPage loads while already signed in (a page restored from the back/forward cache), go to / with replace instead of starting a new sign-in. Together with inbuxa/inbuxa-server#403 the whole sign-in chain collapses into the dashboard entry, and Back from there exits the app.
Reported on the forum (https://community.coffeylabs.org/t/232, post 27): in the installed app, Back goes to the login page instead of leaving the app.
Each step of signing in or out adds a history entry:
- `startAuthFlow` (`src/services/auth/oauth.ts:202`) goes to the server's sign-in page with `window.location.href`
- `endSession` (`src/services/auth/session.ts`) defaults to `window.location.href`
- `signOut` (`src/services/auth/signOut.ts`) uses `window.location.href` for the end-session URL and `navigate('/login')`
Fix: `location.replace` in those three places and `navigate('/login', { replace: true })`; and when `LoginPage` loads while already signed in (a page restored from the back/forward cache), go to `/` with replace instead of starting a new sign-in. Together with inbuxa/inbuxa-server#403 the whole sign-in chain collapses into the dashboard entry, and Back from there exits the app.
Fixed in #222. Starting sign-in, an ended session and signing out now replace the page instead of adding to the history, and /login with a session in hand goes on into the console. Back from the installed app leaves it once the server side (inbuxa/inbuxa-server#403) is out too. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next console RC.
Fixed in #222. Starting sign-in, an ended session and signing out now replace the page instead of adding to the history, and /login with a session in hand goes on into the console. Back from the installed app leaves it once the server side (inbuxa/inbuxa-server#403) is out too. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next console RC.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Reported on the forum (https://community.coffeylabs.org/t/232, post 27): in the installed app, Back goes to the login page instead of leaving the app.
Each step of signing in or out adds a history entry:
startAuthFlow(src/services/auth/oauth.ts:202) goes to the server's sign-in page withwindow.location.hrefendSession(src/services/auth/session.ts) defaults towindow.location.hrefsignOut(src/services/auth/signOut.ts) useswindow.location.hreffor the end-session URL andnavigate('/login')Fix:
location.replacein those three places andnavigate('/login', { replace: true }); and whenLoginPageloads while already signed in (a page restored from the back/forward cache), go to/with replace instead of starting a new sign-in. Together with inbuxa/inbuxa-server#403 the whole sign-in chain collapses into the dashboard entry, and Back from there exits the app.Fixed in #222. Starting sign-in, an ended session and signing out now replace the page instead of adding to the history, and /login with a session in hand goes on into the console. Back from the installed app leaves it once the server side (inbuxa/inbuxa-server#403) is out too. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next console RC.