@microsoft/teams.api/dist/auth/json-web-token.d.ts

<p> <a href="https://www.npmjs.com/package/@microsoft/teams.api" target="_blank"> <img src="https://img.shields.io/npm/v/@microsoft/teams.api/latest" /> </a> <a href="https://www.npmjs.com/package/@microsoft/teams.api?activeTab=code" t

import { JwtPayload } from 'jwt-decode';
import { CallerType } from './caller.js';
import { IToken } from './token.js';

type JsonWebTokenPayload = JwtPayload & {
    readonly [key: string]: any;
};
declare class JsonWebToken implements IToken {
    get audience(): string | string[] | undefined;
    get issuer(): string | undefined;
    get keyId(): string | undefined;
    get appId(): string;
    get appDisplayName(): string | undefined;
    get tenantId(): string | undefined;
    get version(): string | undefined;
    get serviceUrl(): string;
    get from(): CallerType;
    get fromId(): string;
    get expiration(): number | undefined;
    private readonly _value;
    private readonly _payload;
    /**
     * Typed accessor for an already-validated JWT payload. This constructor
     * performs no signature verification, no issuer/audience checks, and no
     * expiry enforcement. Constructing it from an untrusted token does NOT
     * establish trust in the contained claims.
     *
     * Signature verification happens at the HTTP trust boundary via
     * `JwtValidator.validateAccessToken` (packages/apps/src/middleware/auth/
     * jwt-validator.ts). Internal callers may also construct from tokens
     * sourced from trusted identity infrastructure (MSAL, Bot Framework API
     * responses).
     *
     * Callers must not construct this class from raw network input.
     */
    constructor(value: string);
    isExpired(bufferMs?: number): boolean;
    toString(): string;
}

export { JsonWebToken, type JsonWebTokenPayload };