A generic OAuth2 client base implementation for Flow Framework applications
This package is auto-updated.
Last update: 2023-01-09 10:09:28 UTC
This Flow package provides an OAuth 2.0 client SDK. Even though it can be used as a generic OAuth2 client, it was developed as a backing library for the OpenID Connect package. That's why documentation for this package is a bit sparse at the moment and examples for generic use are missing.
At the time of writing (November 2020), this package is actively maintained and there are plans for improving functionality, test coverage and documentation.
This package stores states and tokens as "authorizations" in a dedicated database table.
For example, during the authorization code flow, this package needs to keep track of a "state" in order to make sense of an incoming "finish authorization" request. Another example is the client credentials flow, where an access token is stored in the authorizations table which is needed for executing authorized requests to the respective service.
New Authorization tokens are created with a lifetime of 600 seconds
(10 minutes) by default.
The expiration date is updated during authentication if a different
expires parameter is specified in the OAuth2 access token.
The default token lifetime and frequency of expired tokens to be removed automatically can be configured:
Flownative: OAuth2: Client: garbageCollection: # The probability in percent of a client shutdown triggering a garbage # collection which removes expired tokens. # # Examples: # 1 (would be a 1% chance to clean up) # 20 (would be a 20% chance to clean up) # 0.42 (would be a 0.42 % chance to clean up) probability: 1 token: # default lifetime of new tokens in seconds defaultLifetime: 600
Note: By setting the
null, new tokens won't expire
Authorizations also may contain developer-provided metadata. For example, you may attach an account identifier to an authorization when an authorization process starts and use that information when authorization finishes to make sure that the authorization is only used for a specific account (or customer number, or participant id).
To set metadata, you need to know the authorization id when starting the
authorization code flow. This code could be used in an overloaded
$authorizationId = $oAuthClient->generateAuthorizationIdForAuthorizationCodeGrant($this->appId); $loginUri = $oAuthClient->startAuthorizationWithId( $authorizationId, $this->appId, $this->appSecret, $returnToUri, $scope ); $oAuthClient->setAuthorizationMetadata($authorizationId, json_encode($metadata));
And later, in
finishAuthorization(), you may retrieve the metadata as
$authorization = $this->getAuthorization($authorizationId); $metadata = json_decode($authorization->getMetadata());
By default, access tokens are serialized and stored unencrypted in the "authorizations" database table. You can improve the security of your application by enabling the encrypted-at-rest feature of this package. when active, it will encrypt tokens before storing them in the database and decrypt them automatically when they are retrieved. The secret key which is needed for encryption and decryption is not stored in the database.
This package uses the "ChaCha20-Poly1305-IETF" construction for authenticated encryption / decryption of serialized tokens. It uses the "sodium" PHP extension if installed, or a polyfill implementation in pure PHP.
The OAuth2 Flow package provides a CLI command for generating encryption keys suitable for the currently supported encryption method:
$ ./flow oauth:generateencryptionkey qpBzrH7icQqBKenvk8wTKROv4qcJNxslzdGo3IKXmws=
The key is base64-encoded in order to simplify handling and being able to pass the key via Flow settings.
Set the encryption key via Flow settings (for example in your global "Configuration/Settings.yaml"). Make sure to deploy this setting securely, for example by creating the Settings file during deployment or by using environment variables.
Flownative: OAuth2: Client: encryption: base64EncodedKey: 'qpBzrH7icQqBKenvk8wTKROv4qcJNxslzdGo3IKXmws='
When you have set the encryption key, test that everything is working as
expected. Run your application so that a new authorization is created.
Check the database table
serializedaccesstoken should be empty and the column
encryptedserializedaccesstoken should contain a long string similar to
There are three parts in this string, separated by two dollar signs:
- the construction used for encryption ("ChaCha20-Poly1305-IETF")
- the nonce used for this particular entry ("Mjdj4s9IFrPp6HFK")
- the encrypted data ("k9v3x…KQ==")