ClientTypeResolverInterface
Derives ClientType from a set of already-validated token claims.
The default implementation applies the RFC 9068 rule (service when sub === client_id/azp, else user); an app that needs different logic swaps this service rather than toggling a framework flag.
Synopsis
Section titled “Synopsis”interface ClientTypeResolverInterface
| Implemented by | ClientTypeResolver |
| Since | 1.0.0 |
| Source | Security/Auth/ClientTypeResolverInterface.php |
Methods
Section titled “Methods”| Method | Description |
|---|---|
resolve(array<string, mixed> $claims): ClientType |
resolve()
Section titled “resolve()”abstract public function resolve(array<string, mixed> $claims): ClientType
The validated, raw claim set (pre-TokenClaims).
| Parameter | Type | Description |
|---|---|---|
$claims | array``<``string``, ``mixed``> | The validated, raw claim set (pre-TokenClaims). |
Returns ClientType — Human vs. machine, per RFC 9068.