PushedAuthorizationRequest
in package
The result of `AxiamClient::oidcPar()` (CONTRACT.md §26.1).
The server answered 201 — RFC 9126 §2.2 specifies Created, and a success predicate
written === 200 would treat every successful push as a failure.
$state, $nonce and $codeVerifier are carried straight through from the
AuthorizationRequest that was pushed: §26.2 rule 1 forbids a second generator, and
rule 6 wants exactly one verifier so there is no second place for the two to disagree.
Table of Contents
Properties
- $codeVerifier : Sensitive
- $expiresIn : int
- $nonce : string
- $requestUri : Sensitive
- $state : string
- $url : string
Methods
- __construct() : mixed
Properties
$codeVerifier
public
Sensitive
$codeVerifier
$expiresIn
public
int
$expiresIn
$nonce
public
string
$nonce
$requestUri
public
Sensitive
$requestUri
$state
public
string
$state
$url
public
string
$url
Methods
__construct()
public
__construct(string $url, Sensitive $requestUri, int $expiresIn, string $state, string $nonce, Sensitive $codeVerifier) : mixed
Parameters
- $url : string
-
Where to redirect the user agent. Carries exactly
client_idandrequest_uri— the server refuses a request that mixes arequest_uriwith inline authorization parameters rather than merging them, because merging is where parameter confusion lives (§26.2 rule 2). - $requestUri : Sensitive
-
The opaque, single-use handle. Sensitive per §26.5: between the push and the redirect it is a bearer handle to a fully-formed authorization request, and a log line is the wrong place for it to sit for the length of that window.
- $expiresIn : int
-
The handle's lifetime in seconds; not advisory (§26.2 rule 3).
- $state : string
-
The value to compare against the
statethe IdP returns. - $nonce : string
-
The value that must equal the ID token's
nonceclaim. - $codeVerifier : Sensitive
-
The PKCE verifier to pass into
oidcExchange().