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

Deprecate client-side logIn #13

Open
jmileham opened this issue May 9, 2018 · 0 comments
Open

Deprecate client-side logIn #13

jmileham opened this issue May 9, 2018 · 0 comments

Comments

@jmileham
Copy link
Member

jmileham commented May 9, 2018

The JS client is designed for client-side usage. Login doesn't need to be part of the JS client because a proper integration of TestTrack with an authenticated app will involve a server-side client like test_track_rails_client as well. That server side library will provide an updated visitor ID to the JS client upon successful login and all subsequent JS requests should use it.

This may mean refreshing JS client state after an authentication API call to use the new visitor ID in single-page apps.

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

1 participant