Struct Completion 

pub struct Completion<S: ScopePiiReader> {
    pub id_assertion: IdAssertion<S>,
    pub tokens: TokenResponse,
    pub redirect_to: RelativePath,
}

Verified OIDC authentication outcome.

[super::RelyingParty::complete] returns this; the consumer’s callback_handler typically: (1) issues session cookies from tokens (encrypting refresh_token via [crate::TokenCipher]), (2) redirects to redirect_to (the after_login captured at start time).

id_assertion is the verified identity (sub, iss, aud, exp, iat, nonce, plus scope-bounded PII gated by S). tokens is the raw OAuth response (access_token + refresh_token + expires_in). redirect_to is the RelativePath round-tripped from start.

Scope narrowing carries through to id_assertion: a Completion<scopes::Openid> cannot reach email() even via the public id_assertion field, because IdAssertion::email itself requires the HasEmail bound on S.

use pas_external::oidc::{Completion, Openid};

fn _compile_fail(c: &Completion<Openid>) -> &str {
    c.id_assertion.email() // ERROR: method `email` requires `HasEmail`
}

Fields

id_assertion: IdAssertion<S>

tokens: TokenResponse

redirect_to: RelativePath

Trait Implementations

impl<S: Debug + ScopePiiReader> Debug for Completion<S>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.