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

Passing access_token after signup #366

Closed
ACPK opened this issue Sep 1, 2015 · 3 comments
Closed

Passing access_token after signup #366

ACPK opened this issue Sep 1, 2015 · 3 comments

Comments

@ACPK
Copy link

ACPK commented Sep 1, 2015

I'm bring to life an old app (early 2015) that used devise_token, and noticed that the access_token, UID, expiry, and client are no longer getting passed after a user signs up. The site allows unconfirmed access, so how would I pass the header info after signup?

@ACPK ACPK closed this as completed Sep 1, 2015
@ACPK
Copy link
Author

ACPK commented Sep 1, 2015

It works locally but not on production.

@ACPK ACPK reopened this Sep 1, 2015
@ghost
Copy link

ghost commented Sep 5, 2015

As for me, it passed right way:
< HTTP/1.1 200 OK
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< access-token: OobH67eo1CotXHeUSSAgSw
< token-type: Bearer
< client: M7G7TbBxtacoFPm6OTKEcg
< expiry: 1442655591
< uid: test@test.test
< Content-Type: application/json; charset=utf-8
< ETag: W/"2c2ca7fd01e1597558b559555effe16f"
< Cache-Control: max-age=0, private, must-revalidate
< X-Request-Id: 3d59b70f-198a-4fc2-b9fd-383e3c086b97
< X-Runtime: 0.707628
< Connection: close

@zachfeldman
Copy link
Contributor

Seems like this issue has an accepted solution, so closing for now.

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

2 participants