Download the PHP package pelmered/laravel-http-client-auth-helper without Composer

Laravel HTTP Client Auth helper 🤝

An easy-to-use helper for Laravel HTTP Client to make manage API requests with a two-step auth flow. For example, OAuth2 or refresh tokens to get a new short-lived access token.\ This helper takes care of all the headaches and boilerplate code with a simple and easy-to-use interface.

Features:

• Automatically fetches new access tokens when needed.
• Automatically caches the access tokens for their lifetime.
• Extends the Laravel HTTP Client to make it straightforward to use. Se the usage section below for examples.
• Supports common auth flows like OAuth2 and refresh tokens with most grant types.

Vision, roadmap & plans for the future

I want to support as many common auth flows as possible.\ If you have a use case that is not super obscure, please open an issue where you provide as much detail as possible, or submit a PR with a working solution.

Plans for 1.1 - Milestone

• Automatically refresh tokens in the background before they expire.
• Add support for authorization_code and implicit OAuth2 grants.
• Tokens owned by a model. For example, tokens associated with a user model rather than the whole application.

Table of contents

• Requirements
• Vision, roadmap & plans for the future
• Contributing
  • Issues & Bug Reports
• Installation
• Options reference
  • scopes - array
  • authType - string
  • grantType - string
  • tokenType - string
  • tokenName - string
  • expires - int|string|Closure|Carbon
  • accessToken - string|Closure
  • tokenTypeCustomCallback - ?Closure
  • cacheKey - ?string
  • cacheDriver - ?string
• Usage
  • Minimal example:
  • All parameters with default values:
  • For full type safety, you can also provide objects instead of arrays:
  • Customize with callbacks
  • Integration tips

Requirements

• PHP 8.2 or higher
• Laravel 10

Vision, roadmap & plans for the future

I want to support as many common auth flows as possible.\ If you have a use case that is not super obscure, please open an issue where you provide as much detail as possible, or submit a PR.

Contributing

See Contribution Guide before sending pull requests.

Issues & Bug Reports

When you are submitting issues, I appreciate if you could provide a failing test case. That makes my job a lot easier.\ I will try to fix reported issues as soon as possible, but I do this in my spare time, so I might not be able to do it immediately.

Installation

Options reference

scopes - array

Scopes to send when requesting an access token. Typically only used for OAuth2 flows.\ Possible options: array with strings Default: []

authType - string

The type of authorization for the refresh token request.\ Possible options: Credentials::AUTH_TYPE_BEARER, Credentials::AUTH_TYPE_BODY, Credentials::AUTH_TYPE_QUERY, Credentials::AUTH_TYPE_BASIC, Credentials::AUTH_TYPE_CUSTOM,\ Default: Credentials::AUTH_TYPE_BEARER (='Bearer')

grantType - string

Grant type for OAuth2 flows.\ Possible options: Credentials::GRANT_TYPE_CLIENT_CREDENTIALS, Credentials::GRANT_TYPE_PASSWORD_CREDENTIALS (authorization_code and implicit grants are not yet supported. See issue #3)\ Default: Credentials::GRANT_TYPE_CLIENT_CREDENTIALS (='client_credentials')

tokenType - string

How the access token should be applied to all subsequent requests.\ Possible options: AccessToken::TOKEN_TYPE_BEARER, AccessToken::TOKEN_TYPE_QUERY, AccessToken::TOKEN_TYPE_CUSTOM \ Default: AccessToken::TOKEN_TYPE_BEARER (='Bearer')

tokenName - string

The name of the token field. This only applies for when the token is applied as a query parameter or to the body of the request.\ Possible options: Any string\ Default: 'token'

expires - int|string|Closure|Carbon

This determines when the access token expires.\ Possible options: \ integer - for how long until expiry in seconds)\ string - Can be key of the field in response that contains the expiry of the token. Can also be a string with a date. This is then parsed by Carbon::parse so any format that Carbon can parse is acceptable.\ Closure - A closure that receives the refresh response and can return any other acceptable value (integer, string or Carbon object).\ Carbon - A Carbon object with the time of the expiry.\ Default: 3600

accessToken - string|Closure

This is where the access token can be found on the refresh response.\ Possible options:\ string - The key of the access token in the refresh response.\ Closure - A closure that receives the refresh response and should return the token as a string.\ Default: 'access_token'

tokenTypeCustomCallback - ?Closure

A callback for giving dull control of how the authentication should be applied. The closure receives the Http client and should return a new Http Client where the auth information has been appended.\ Possible options:\ Any closure that returns a Http Client (Illuminate\Http\Client\PendingRequest).\ Default: null

cacheKey - ?string

The cache key that should be used to save the access tokens. If left empty, it will be generated based on the refresh URL.\ Possible options:\ Default: null

cacheDriver - ?string

The cache driver/store that should be used for storing the access tokens. If left empty, the Laravel default will be used.\ Possible options:\ Default: null

Usage

It's really simple to use. Just add the withRefreshToken method to your HTTP request and provide the necessary parameters. No configuration needed.

Minimal example:

All parameters with default values:

For full type safety, you can also provide objects instead of arrays:

Customize with callbacks

You can also provide callbacks for expires, auth_type, and access_token to customize the behavior.

Custom auth for refreshing token:

For more examples, check out the Macro tests.

Integration tips

If you use the same token in multiple places, you can create the client only once and save it. For example:

to use it later like this:

You can also resolve it in the container if you want. In your service provider:

and then use it anywhere like this: