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

Client should store token string and not the token object #95

ekryski opened this Issue Mar 6, 2016 · 2 comments


None yet
2 participants
Copy link

ekryski commented Mar 6, 2016

I thought I had fixed this but it looks like you need to reference hook.params.token.value in


This comment has been minimized.

Copy link

PhilWhitehurst commented Mar 18, 2016

It doesn't send the token when using a service over io sockets am I missing something? I want to authorise a service but it is looking for an authorisation header that isn't sent with a socket. So although I can authenticate I can also use the service if not authenticated


This comment has been minimized.

Copy link
Member Author

ekryski commented Mar 18, 2016

@PhilWhitehurst it definitely should. Can you post a link to your code so that we can see what might be going on? Alternatively, take a look at this fully working example for a comparison.

@ekryski ekryski modified the milestone: 0.6 Mar 26, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.