Application.createSsoUrl()
parseSsoResponse

consume a response uri, get the JWT, assert it’s legit, then get the
account
sso request is now using a JWT
irt_jti
id_token is now jwtResponse
parseSsoResponse -> handleSsoResponse, add responseMode param
create and get api keys for an account

trying out nock in tests
implement cache regions

there should be a new Cache for every cache region
rewrite account tests without knock

just stub out the request executor

it wasn’t obvious how to get nock.get and nock.post to accept a regexp
always requested encrypted secrets when getting api keys
Application.getApiKey

tests to assert that:
 
* we get a single ApiKey instance back

* the cache will transparently find and cache any nested items in a collection response
don’t expose instantiate, use base64 url safe encoding for salt
caching of api keys, un-encrypted, then decrypt on get
irt_jti -> irt
fix tests, start asserting cache requirements in tests
messy first implementation of Application.authenticateApiRequest

did quick integration testing with a demo connect app, seems like it’s
doing the right thing
ability to set and get scopes on tokens
ability to set ttl
cleanup: break out authentication strategies and errors into files
misc cleanup