-
Notifications
You must be signed in to change notification settings - Fork 309
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
NAS-132648 / 25.04 / query param handling for auth tokens #11080
base: master
Are you sure you want to change the base?
Conversation
…e. forward query params on redirect in auth-guard.service
The approach so far is to forward query params on redirect to However, this isn't working like I'd expect. Seems that |
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #11080 +/- ##
==========================================
- Coverage 82.35% 82.33% -0.02%
==========================================
Files 1630 1644 +14
Lines 57229 57522 +293
Branches 5915 5933 +18
==========================================
+ Hits 47130 47362 +232
- Misses 10099 10160 +61 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be redirecting fine for me:
2024-11-21.11.03.57.mov
BTW, I don't know if tokens in browser history is kosher. |
…t connection to the NAS has opened at least once. adds queryToken to signin.store state.
…ken from signin.store state.
Changes:
Testing:
One method:
localStorage
https:
check inAuthService.setQueryToken
midclt call auth.generate_token
localhost:4200/storage/disks?token=<token>
Downstream