iya-sts
    Preparing search index...

    Certifies and registers a remote PEP's RFC 7523 assertion key from the PEP's own certificate request (#1827's follow-up, phase 3). The service never holds the private key.

    Index
    • Builds the act over its dependencies.

      Parameters

      • deps: PepCredentialDeps

        the logger, audit log, error codes, person key register, service accounts, roles, chain builder and realm

      Returns export=

    PEP_CLIENT_ID: "sts-remote-pep" = PEP_CLIENT_ID

    The client the PEP's token is issued through.

    • Certifies the key in a remote PEP's own PKCS #10 request from the realm's Issuing CA and registers it as the PEP entry's RFC 7523 key.

      The entry must exist (STS-XACML-0298), be a service account (STS-XACML-0299) and hold REMOTE_PEPS (STS-XACML-0301). The request's names are ignored; the leaf names urn:sts:sa:<name>. Audited, with no key material.

      Parameters

      • Optionalbody: any

        name (or pep): the PEP's username; csr: the request (PEM or base64 DER); optionally label, days and revokePrevious

      Returns Promise<CredentialResult>

      a promise of the result: the certificate, its chain, kid, urn, and the PEP's environment; or a refusal with its code

    • Returns the dependencies built from the real modules. Every module is reached LAZILY: person_assertions.js and roles.js are on app.js's chain and service_accounts.ts and pki.js are libraries, all loaded long before an administrator issues anything.

      Returns PepCredentialDeps

      the dependencies