iya-sts
    Preparing search index...
    verifyAccessToken: (
        token: any,
        req: any,
        opts?: any,
    ) =>
        | {
            claims?: undefined;
            code: any;
            error: any;
            ok: boolean;
            status: number;
            username?: undefined;
            why: any;
        }
        | {
            claims: any;
            code?: undefined;
            error?: undefined;
            ok: boolean;
            status?: undefined;
            username: string;
            why?: undefined;
        } = ...

    Type Declaration

      • (
            token: any,
            req: any,
            opts?: any,
        ):
            | {
                claims?: undefined;
                code: any;
                error: any;
                ok: boolean;
                status: number;
                username?: undefined;
                why: any;
            }
            | {
                claims: any;
                code?: undefined;
                error?: undefined;
                ok: boolean;
                status?: undefined;
                username: string;
                why?: undefined;
            }
      • Verifies an access token for the debugger in RFC 9068 section 4's order, then its sender constraints, the permission and the subject.

        The signature is checked against the default realm's keys, and the subject must still be a console administrator.

        Parameters

        • token: any

          the access token

        • req: any

          the express request

        • Optionalopts: any

          optional; presented is true when the token came on this request's Authorization header, and scheme says how it was sent

        Returns
            | {
                claims?: undefined;
                code: any;
                error: any;
                ok: boolean;
                status: number;
                username?: undefined;
                why: any;
            }
            | {
                claims: any;
                code?: undefined;
                error?: undefined;
                ok: boolean;
                status?: undefined;
                username: string;
                why?: undefined;
            }

        { ok: true, claims, username } or { ok: false, status, code, error, why }