AXIAM PHP SDK

ClientAuthMethod : string
in package

How a client proves its identity at the token endpoint (RFC 8705 §2, OIDC Core §9 naming).

Only the methods AXIAM actually implements are representable. There is deliberately no none variant: every AXIAM client is confidential today (see handle_authorization_code), and adding a public-client value here before the rest of the server understands one would let an operator register a client whose authentication is silently skipped.

An open enum. A value this SDK's copy of the spec does not list decodes to self::Unknown rather than failing the response it arrived in (CONTRACT.md §27.11 rule 1). Its own wire spelling is the empty string, which no server value is, so carrying an unrecognised value back into an update is refused by the server rather than written as a spelling it never used. A match over these cases needs an Unknown arm.

Table of Contents

Cases

ClientSecretPost  = 'client_secret_post'
The wire value `client_secret_post`.
PrivateKeyJwt  = 'private_key_jwt'
The wire value `private_key_jwt`.
SelfSignedTlsClientAuth  = 'self_signed_tls_client_auth'
The wire value `self_signed_tls_client_auth`.
TlsClientAuth  = 'tls_client_auth'
The wire value `tls_client_auth`.
Unknown  = ''
A value this SDK's copy of the spec does not list; see the type's summary.

Methods

fromWire()  : self
Parses a wire value into a ClientAuthMethod, mapping an unrecognised one to {@see self::Unknown}.

Cases

Unknown

A value this SDK's copy of the spec does not list; see the type's summary.

Methods

fromWire()

Parses a wire value into a ClientAuthMethod, mapping an unrecognised one to {@see self::Unknown}.

public static fromWire(string $value) : self

Never throws. A parse error here would fail the whole response the value arrived in, so one unrecognised field of one record would take down the page it was on (§27.11 rule 1). A match over this enum needs an Unknown arm.

Parameters
$value : string
Return values
self
On this page

Search results