You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client shows publisher group. User is not logged in.
Actual result
Client shows normal Hypothesis groups. User is logged in to their normal Hypothesis account.
Notes
The issue is that in this context, the host page (the publisher account test site) includes a services config for the client but the grantToken is null. If the grant token is null we fall back to trying to load access tokens from local storage.
Since the apiUrl config param is the same for this "third party service" as it is for the regular Hypothesis service, the storageKey() function returns the same key that was used to store OAuth tokens for the regular Hypothesis service.
Consequently the client ends up using the saved access token and the user ends up logged in to their regular Hypothesis account.
The text was updated successfully, but these errors were encountered:
robertknight
changed the title
Client uses OAuth tokens for Hypothesis accounts when a third-party service hosted by Hypothesis is configured but no grant token is provided
User can end up logged into regular Hypothesis account on a page configured to use a third party account
Nov 9, 2017
Steps to reproduce
Expected result
Client shows publisher group. User is not logged in.
Actual result
Client shows normal Hypothesis groups. User is logged in to their normal Hypothesis account.
Notes
The issue is that in this context, the host page (the publisher account test site) includes a
services
config for the client but thegrantToken
is null. If the grant token is null we fall back to trying to load access tokens from local storage.Since the
apiUrl
config param is the same for this "third party service" as it is for the regular Hypothesis service, thestorageKey()
function returns the same key that was used to store OAuth tokens for the regular Hypothesis service.Consequently the client ends up using the saved access token and the user ends up logged in to their regular Hypothesis account.
The text was updated successfully, but these errors were encountered: