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

Authenticated session is redirected to login in fastboot on 1.4.0 #1420

Closed
billdami opened this issue Aug 13, 2017 · 4 comments
Closed

Authenticated session is redirected to login in fastboot on 1.4.0 #1420

billdami opened this issue Aug 13, 2017 · 4 comments

Comments

@billdami
Copy link

This behavior appears to be a regression in 1.4.0, as I am not able to reproduce it if I downgrade to 1.3.0.

On ember-simple-auth 1.4.0, ember 2.14.1, and fastboot 1.0.1, using the required application session-store that extends ember-simple-auth/session-stores/cookie, it seems that authenticated sessions are either not found or respected by simple-auth's AuthenticatedRouteMixin in fastboot, as the server will return a 307 redirect to the login route. However, upon client side boot, the UnauthenticatedRouteMixin for this route will take over and transition the user back to the intended destination. As noted above, if I downgrade to 1.3.0, this does not happen at all, and I am able to access authenticated routes in fastboot with no redirects when authenticated.

@marcoow marcoow added the triage label Aug 14, 2017
@willviles
Copy link
Contributor

willviles commented Aug 14, 2017

This perhaps could be related to #1138?

@billdami
Copy link
Author

@willviles yeah I'd say its extremely likely that this is the same issue, given that it doesnt happen on 1.3.0

@Zorig
Copy link

Zorig commented Oct 23, 2017

This is also happened to me either. On fastboot i used cookieStore, and in network requests cookie also sent. Still simpleauth redirect to login page. It also keep logging error there is no route named index

@marcoow
Copy link
Member

marcoow commented Dec 19, 2017

Closing as #1138 has been closed as well and there were no new reports. Please reopen if this is still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants