Switch Syncstorage loadtester Tokenserver auth from browserid to oauth

[data-sync-user]

The syncstorage loadtester supports running in 2 modes depending on the SERVER_URL env var setting:

1. If specified with a URL fragment it treats the url as the syncstorage endpoint with the fragment being the syncstorage’s SYNC_MASTER_SECRET of which the hawk auth is signed with (which it will “forge” hawk credentials with, without communicating to Tokenserver)
2. If no fragment, it assumes it’s a Tokenserver endpoint, of which it signs in with mocked credentials to be issued the hawk credentials (the default, pointing to tokenserver stage)

In the case of the Tokenserver endpoint (#2), the loadtester only uses the now deprecated/no longer supported browserid assertions to communicate with Tokenserver, which will no longer work with modern version of Tokenserver. This should be converted to use OAuth access tokens instead.

┆Issue is synchronized with this Jira Task

[data-sync-user]

➤ Philip Jenvey commented:

The tokenserver integration test suite might provide some guidance on how to make this conversion, as it also “mocked” both such credentials. The browserid support has been removed but looking at the old code that supported browserid vs oauth might be insightful.