Struct Interactive 

struct Interactive {

    sealer: CookieSealer,
    backend: SessionBackend,
    authorization_endpoint_cfg: Option<String>,
    token_endpoint_cfg: Option<String>,
    redirect_uri: String,
    redirect_path: String,
    scope: String,
    session_cookie: String,
    flow_cookie: String,
    cookie_path: String,
    session_lifetime: Duration,
    refresh_enabled: bool,
    logout_path: Option<String>,
    post_logout_redirect_uri: String,
    authz_endpoint_resolved: Mutex<Option<String>>,
    token_endpoint_resolved: Mutex<Option<String>>,
}

Interactive-mode configuration, present only when bearer_only: false.

Fields

sealer: CookieSealer

backend: SessionBackend

authorization_endpoint_cfg: Option<String>

token_endpoint_cfg: Option<String>

redirect_uri: String

redirect_path: String

Path portion of redirect_uri, matched to detect the callback.

scope: String

session_cookie: String

flow_cookie: String

cookie_path: String

Path attribute for the session and flow cookies. Scoping this to the app’s subpath (e.g. /app_a) lets two openid-connect nodes on distinct subpaths hold independent sessions in the browser. Defaults to /.

session_lifetime: Duration

refresh_enabled: bool

session.refresh (default true): redis-mode only — whether a near-expiry access token is transparently refreshed before identity is attached. Ignored in cookie mode, which never refreshes.

logout_path: Option<String>

post_logout_redirect_uri: String

authz_endpoint_resolved: Mutex<Option<String>>

token_endpoint_resolved: Mutex<Option<String>>