DeviceToken
in package
The result of `AxiamClient::authenticateDevice()` — the mTLS device login (CONTRACT.md §6.1 rules 6-10, contract 1.51).
A readonly DTO, mirroring LoginResult's and UserInfo's own shape (D-09: a typed record, never a raw array/stdClass).
There is no refresh token (§6.1 rule 6, server decision D-6 of the dogfooding
remediation plan). A device re-authenticates by calling authenticateDevice() again,
which costs one TLS handshake — the SDK's §9 single-flight refresh guard has nothing
to spend on this credential, and never tries.
Table of Contents
Properties
- $accessToken : Sensitive
- $expiresIn : int
- $tokenType : string
Methods
- __construct() : mixed
Properties
$accessToken read-only
public
Sensitive
$accessToken
$expiresIn read-only
public
int
$expiresIn
$tokenType read-only
public
string
$tokenType
Methods
__construct()
public
__construct(Sensitive $accessToken, string $tokenType, int $expiresIn) : mixed
Parameters
- $accessToken : Sensitive
-
The service-account access token this device now holds. Certificate-bound when AXIAM itself terminated the TLS handshake (§6.1 rule 9) — a REST request without the same certificate, or a gRPC call on a listener not requesting client certificates, is refused.
- $tokenType : string
-
Always
"Bearer"(§6.1 rule 6). Does not say whether the token is certificate-bound — see AxiamClient::validateToken() /introspectToken()for that. - $expiresIn : int
-
The access-token lifetime in seconds (server default 900).