Download the PHP package dvsa/authentication-cognito without Composer
On this page you can find all versions of the php package dvsa/authentication-cognito. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dvsa/authentication-cognito
More information about dvsa/authentication-cognito
Files in dvsa/authentication-cognito
Package authentication-cognito
Short Description A wrapper around the AWS SDK (Cognito)
License MIT
Informations about the package authentication-cognito
DVSA Cognito Authentication Wrapper
A thin authentication wrapper around the aws-sdk, focusing on the Cognito endpoints.
Installing
The recommended way to install is through Composer.
Usage
Caching the JSON Web Key Set
Verifying a token requires Cognito's public signing keys. With no cache configured the client
re-downloads the JWKS on every decodeToken() call — PHP shares nothing between requests, so
on a web application that is an outbound HTTPS round trip to Cognito per authenticated request.
Pass any PSR-6 cache pool to avoid it:
Keys are looked up by key id and only re-fetched when an unrecognised one turns up, so Cognito key rotation is still picked up automatically — there is nothing to invalidate by hand.
Tuning
The defaults are chosen to be safe; most applications will not need to change them.
expiresAfterbounds how long a cached JWKS is trusted. A key Cognito has revoked is still a known key id, so it never triggers the unknown-key re-fetch that would evict it; without an expiry the client would go on accepting tokens signed by that key. Passingnullhands the decision to your pool, which for some implementations means the entry never expires.rateLimitcaps re-fetches at 10 per minute. A cache miss is driven by the key id in the incoming token, which is attacker-controlled, so leaving this off lets a stream of tokens bearing unknown key ids become a stream of outbound calls to Cognito. The trade-off is that once the budget is spent, tokens with an unrecognised key id are rejected until the window clears.
A note on trust
The cached JWKS is what signature verification is performed against, so anything able to write to that cache can influence which tokens are accepted. Back it with a store your application trusts to the same degree it trusts its own session storage.
Contributing
Please refer to our Contributor Code of Conduct.
All versions of authentication-cognito with dependencies
ext-json Version *
ext-openssl Version *
aws/aws-sdk-php Version ^3.383
dvsa/contracts Version ^1.3
firebase/php-jwt Version ^7.0
guzzlehttp/guzzle Version ^7.15.3
guzzlehttp/psr7 Version ^2.13
league/oauth2-client Version ^2.9
psr/cache Version ^1.0 || ^2.0 || ^3.0
psr/http-client Version ^1.0.3
psr/http-factory Version ^1.1