Skip to content

[Proof of concept] Certificate Handling Improvements #7473

Open
@Robbie-Microsoft

Description

@Robbie-Microsoft

Core Library

MSAL Node (@azure/msal-node)

Wrapper Library

Not Applicable

Public or Confidential Client?

Confidential

Description

How can we simply (for the developer) the way that certificate information - SHA256 thumbprint, private key, and x5 - is passed into MSAL Node when the Confidential Client flow is used?

Currently, the developer can pass the following into the MSAL app's configuration object:

export type NodeAuthOptions = {
    ...
    clientCertificate?: {
        /**
         * @deprecated Use thumbprintSha2 property instead. Thumbprint needs to be computed with SHA-256 algorithm.
         * SHA-1 is only needed for backwards compatibility with older versions of ADFS.
         */
        thumbprint?: string;
        thumbprintSha256?: string;
        privateKey: string;
        x5c?: string;
    };
    ...
}

Metadata

Metadata

Labels

confidential-clientIssues regarding ConfidentialClientApplicationsmsal-nodeRelated to msal-node packagequestionCustomer is asking for a clarification, use case or information.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions