Download the PHP package horde/oauth without Composer
On this page you can find all versions of the php package horde/oauth. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package oauth
Short Description OAuth 1.0a, OAuth 2.0 and OpenID Connect library
License BSD-2-Clause
Homepage https://www.horde.org/libraries/Horde_Oauth
Informations about the package oauth
Horde\OAuth
OAuth 1.0a consumer. OAuth 2.0 authorization server and client. OpenID Connect provider library for the Horde Project but with virtually no framework ties.
Features
OAuth 1.0a Client (Horde\OAuth\V10a\Client)
- 3-legged authorization flow: Request token, user authorization, access token exchange
- PSR-18 HTTP client: Inject any compliant HTTP client (horde/http, Guzzle, Symfony HttpClient etc.)
- Signature methods: HMAC-SHA1, HMAC-SHA256, RSA-SHA1, PLAINTEXT
- Authenticated HTTP client: PSR-18 decorator that signs every outgoing request with OAuth 1.0a credentials
- Immutable value objects for consumer credentials, tokens and provider endpoints
OAuth 2.0 Client (Horde\OAuth\Client)
- Authorization code flow with PKCE support
- Token refresh with automatic retry
- OpenID Connect provider discovery
- Incremental consent
- Authenticated HTTP client with transparent token refresh
OAuth 2.0 Server (Horde\OAuth\Server)
- Authorization code, client credentials and refresh token grants
- PKCE verification (S256, plain)
- Token introspection and revocation endpoints
- Bearer token middleware (PSR-15)
- Repository pattern with in-memory reference implementation
OpenID Connect (Horde\OAuth\Oidc)
- ID token building with standard claims
- Discovery and JWKS endpoints
- Userinfo endpoint
- Scope-to-claims mapping
Installation
Quick Example: OAuth 1.0a Client
Making authenticated API calls
Quick Example: OAuth 2.0 Client
Architecture
This library depends only on PSR interfaces (psr/http-client,
psr/http-message, psr/http-factory, psr/http-server-handler,
psr/http-server-middleware) and horde/jwt for JWT token handling. It does
not depend on any concrete HTTP implementation, allowing consumers to bring
their own PSR-18 client. But they really shouldn't. The horde/http library is all they need.
See doc/ARCHITECTURE.md for design principles and rationale and doc/UPGRADING.md for migration guidance from 2.x.
Relevant RFCs
- RFC 5849 - OAuth 1.0a
- RFC 6749 - OAuth 2.0
- RFC 7636 - PKCE
- RFC 7662 - Token Introspection
- OpenID Connect Core 1.0
Requirements
- PHP 8.1 or later
ext-hashext-jsonext-openssl
License
BSD-2-Clause. See LICENSE for details.
All versions of oauth with dependencies
horde/jwt Version ^1 || dev-FRAMEWORK_6_0
psr/http-message Version ^2
psr/http-factory Version ^1.0.2
psr/http-client Version ^1.0.3
psr/http-server-handler Version ^1.0.2
psr/http-server-middleware Version ^1.0.2
ext-hash Version *
ext-json Version *
ext-openssl Version *