Migrating to AccountsJS JWT from Meteor Login Token

[KeithGillette]

We have an Apollo GraphQL project that we are migrating away from MeteorJS. We have implemented custom UserSignIn and UserSignOut mutations and integrated with ApolloLink on our Angular client application to put the Meteor loginToken on an authentication-token header which is hashed on the server using Meteor Accounts._hashLoginToken and then used to read the user from the users collection in order to put the userId on the GraphQL context in an ApolloServer context function to make it available to authorize GraphQL operations. If we don't want to replace our custom User GraphQL type, how might we convert our UserSignIn and UserSignOut mutations to use JWT instead of Meteor's login token (assuming that getting AccountsJS to work with Meteor's hashed login tokens is a much bigger lift)?

[KeithGillette]

Fumbled my way through figuring this out:

Our existing UserSignIn mutation now returns LoginResult obtained from calling AccountsServer.loginWithService() in the UserSignIn resolver method, which we then add to localstorage using AccountsClient.setTokens() in the Apollo Client UserSignIn mutation subscription handler, allowing us to return the token in the headers using ApolloLink and in the Subscriptions WebSocket connection parameters using AccountsClient.getTokens(). Our UserSignOut mutation then calls AccountsServer.logout() with the Apollo Client UserSignOut mutation subscription handler calling AccountsClient.clearTokens().