This adds a new access token authenticator, which decouples application assertions from access token assertions (authentication vs. authorization). It also adds a key resolver, which depends on a not-yet-released version of nJwt (work in progress here https://github.com/jwtk/njwt/pull/43).
This authenticator will be used with the next patch release of express-stormpath, so that access tokens issued by client API will validate correctly - so long as they are issued by the same stormpath application, we will still retain that behavior, we just need to introduce the key resolving.
Coverage decreased (-1.5%) to 88.023% when pulling 876fbabfad7f52d02c08900e2448a239bae1c623 on access-token-authenticator into 2d0b7368dbaed5a874d83b19884b2a3003cc654c on master.
Coverage decreased (-1.5%) to 88.023% when pulling 6d4ba1b61d159be8a54fcb3e97ef6bda0bb69c3e on access-token-authenticator into 2d0b7368dbaed5a874d83b19884b2a3003cc654c on master.
Coverage decreased (-1.5%) to 88.027% when pulling 5696bf6d885b7768c9e8f94de22fa26e0e30ab91 on access-token-authenticator into 2d0b7368dbaed5a874d83b19884b2a3003cc654c on master.
Coverage decreased (-1.5%) to 88.027% when pulling 2ee9d93837024736d3386715a96b640e7389d516 on access-token-authenticator into 2d0b7368dbaed5a874d83b19884b2a3003cc654c on master.
Coverage decreased (-1.5%) to 88.027% when pulling ef1eb3234a2c72fa9d9926c35501d8defa6e7c77 on access-token-authenticator into 2d0b7368dbaed5a874d83b19884b2a3003cc654c on master.
Coverage decreased (-1.5%) to 88.027% when pulling ef1eb3234a2c72fa9d9926c35501d8defa6e7c77 on access-token-authenticator into 2d0b7368dbaed5a874d83b19884b2a3003cc654c on master.
Coverage decreased (-1.4%) to 88.136% when pulling 9ada1a79b265ce3fc7a35d8c7bbfb02e81b29e2d on access-token-authenticator into 2d0b7368dbaed5a874d83b19884b2a3003cc654c on master.
This adds a new access token authenticator, which decouples application assertions from access token assertions (authentication vs. authorization). It also adds a key resolver, which depends on a not-yet-released version of nJwt (work in progress here https://github.com/jwtk/njwt/pull/43).
This authenticator will be used with the next patch release of express-stormpath, so that access tokens issued by client API will validate correctly - so long as they are issued by the same stormpath application, we will still retain that behavior, we just need to introduce the key resolving.