-
Notifications
You must be signed in to change notification settings - Fork 266
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 use Auth Providers when running locally #9138
Comments
We should get this working, bugs are creeping in because people are developing / testing AP group use cases (basically anything to do with permissions, roles, etc) |
How can you get redirected locally from GH? You need to specify an IP address to be redirected, so or you set local IP or the hosted one. |
The redirect is done locally, so For whoever picks this up, the routing above was previously done only in dev world when serving locally. We'd need to do similar here. In production the redirect is handled via Rancher. |
A unit test would help here but this bug isn't production facing. |
This routing logic may have been tied to Nuxt before it was removed. Maybe we can do something in the Vue config. |
We should ensure that this redirect is not added in production. There should be a There might be an issue with our middleware
however.... in 2.7.5 that serverMiddleware isn't actually used anywhere. We should investigate that side first (bringing up serverMiddleware in post/manual nuxt world). @codyrancher can provide some assistance |
QA will validate if this continues to work on Rancher prod environment |
Pass
|
Setup
Describe the bug
It looks like configuring an Auth Provider, like Github, does not work when serving the dashboard locally (due to the server middleware which redirects /verify-auth to /auth/verify not being wired in). I had to add the following to routes in shell/config/router.js
To Reproduce
Result
redirect after accepting in github redirects to a 404 page
Expected Result
redirect succesfuly closes window and auth provider detail page shown
The text was updated successfully, but these errors were encountered: