Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developer.chrome.com/docs/extensions/reference/api/certificateProvider below:

chrome.certificateProvider | API | Chrome for Developers

Stay organized with collections Save and categorize content based on your preferences.

Use this API to expose certificates to the platform which can use these certificates for TLS authentications.

certificateProvider

Typical usage of this API to expose client certificates to ChromeOS follows these steps:

• The Extension registers for the events onCertificatesUpdateRequested and onSignatureRequested.
• The Extension calls setCertificates() to provide the initial list of certificates after the initialization.
• The Extension monitors the changes in the list of available certificates and calls setCertificates() to notify the browser about every such change.
• During a TLS handshake, the browser receives a client certificate request. With an onCertificatesUpdateRequested event, the browser asks the Extension to report all certificates that it currently provides.
• The Extension reports back with the currently available certificates, using the setCertificates() method.
• The browser matches all available certificates with the client certificate request from the remote host. The matches are presented to the user in a selection dialog.
• The user can select a certificate and thereby approve the authentication or abort the authentication.

• If the user aborts the authentication or no certificate matched the request, the TLS client authentication is aborted.
• Otherwise, if the user approves the authentication with a certificate provided by this Extension, the browser requests the Extension to sign the data to continue the TLS handshake. The request is sent as a onSignatureRequested event.
• This event contains input data, declares which algorithm has to be used to generate the signature, and refers to one of the certificates that were reported by this Extension. The Extension must create a signature for the given data using the private key associated with the referenced certificate. Creating the signature might require prepending a DigestInfo and padding the result before the actual signing.
• The Extension sends back the signature to the browser using the reportSignature() method. If the signature couldn't be calculated, the method has to be called without signature.
• If the signature was provided, the browser completes the TLS handshake.

The actual sequence of steps can be different. For example, the user will not be asked to select a certificate if the enterprise policy to automatically select a certificate is used (see AutoSelectCertificateForUrls and Chrome policies for users).

In the Extension, this can look similar to the following snippet:

function collectAvailableCertificates() {
  // Return all certificates that this Extension can currently provide.
  // For example:
  return [{
    certificateChain: [new Uint8Array(...)],
    supportedAlgorithms: ['RSASSA_PKCS1_v1_5_SHA256']
  }];
}

// The Extension calls this function every time the currently available list of
// certificates changes, and also once after the Extension's initialization.
function onAvailableCertificatesChanged() {
  chrome.certificateProvider.setCertificates({
    clientCertificates: collectAvailableCertificates()
  });
}

function handleCertificatesUpdateRequest(request) {
  // Report the currently available certificates as a response to the request
  // event. This is important for supporting the case when the Extension is
  // unable to detect the changes proactively.
  chrome.certificateProvider.setCertificates({
    certificatesRequestId: request.certificatesRequestId,
    clientCertificates: collectAvailableCertificates()
  });
}

// Returns a private key handle for the given DER-encoded certificate.
// |certificate| is an ArrayBuffer.
function getPrivateKeyHandle(certificate) {...}

// Digests and signs |input| with the given private key. |input| is an
// ArrayBuffer. |algorithm| is an Algorithm.
// Returns the signature as ArrayBuffer.
function signUnhashedData(privateKey, input, algorithm) {...}

function handleSignatureRequest(request) {
  // Look up the handle to the private key of |request.certificate|.
  const key = getPrivateKeyHandle(request.certificate);
  if (!key) {
    // Handle if the key isn't available.
    console.error('Key for requested certificate no available.');

    // Abort the request by reporting the error to the API.
    chrome.certificateProvider.reportSignature({
      signRequestId: request.signRequestId,
      error: 'GENERAL_ERROR'
    });
    return;
  }

  const signature = signUnhashedData(key, request.input, request.algorithm);
  chrome.certificateProvider.reportSignature({
    signRequestId: request.signRequestId,
    signature: signature
  });
}

chrome.certificateProvider.onCertificatesUpdateRequested.addListener(
    handleCertificatesUpdateRequest);
chrome.certificateProvider.onSignatureRequested.addListener(
    handleSignatureRequest);

Types of supported cryptographic signature algorithms.

"RSASSA_PKCS1_v1_5_MD5_SHA1"
Specifies the RSASSA PKCS#1 v1.5 signature algorithm with the MD5-SHA-1 hashing. The extension must not prepend a DigestInfo prefix but only add PKCS#1 padding. This algorithm is deprecated and will never be requested by Chrome as of version 109.

• Must be the DER encoding of a X.509 certificate. Currently, only certificates of RSA keys are supported.

• Must be set to all hashes supported for this certificate. This extension will only be asked for signatures of digests calculated with one of these hash algorithms. This should be in order of decreasing hash preference.

• certificatesRequestId

  number

  Request identifier to be passed to setCertificates.

• certificateChain

  ArrayBuffer[]

  The array must contain the DER encoding of the X.509 client certificate as its first element.

  This must include exactly one certificate.

• All algorithms supported for this certificate. The extension will only be asked for signatures using one of these algorithms.

Types of errors that the extension can report.

"MD5_SHA1"
Specifies the MD5 and SHA1 hashing algorithms.

The types of errors that can be presented to the user through the requestPin function.

"INVALID_PIN"
Specifies the PIN is invalid.

The type of code being requested by the extension with requestPin function.

"PIN"
Specifies the requested code is a PIN.

• userInput

  string optional

  The code provided by the user. Empty if user closed the dialog or some other error occurred.

• error

  "GENERAL_ERROR"
   optional

  Error that occurred while generating the signature, if any.

• Request identifier that was received via the onSignatureRequested event.

• signature

  ArrayBuffer optional

  The signature, if successfully generated.

• attemptsLeft

  number optional

  The number of attempts left. This is provided so that any UI can present this information to the user. Chrome is not expected to enforce this, instead stopPinRequest should be called by the extension with errorType = MAX_ATTEMPTS_EXCEEDED when the number of pin requests is exceeded.

• The error template displayed to the user. This should be set if the previous request failed, to notify the user of the failure reason.

• The type of code requested. Default is PIN.

• The ID given by Chrome in SignRequest.

• certificatesRequestId

  number optional

  When called in response to onCertificatesUpdateRequested, should contain the received certificatesRequestId value. Otherwise, should be unset.

• List of currently available client certificates.

• error

  "GENERAL_ERROR"
   optional

  Error that occurred while extracting the certificates, if any. This error will be surfaced to the user when appropriate.

• Signature algorithm to be used.

• The DER encoding of a X.509 certificate. The extension must sign input using the associated private key.

• Data to be signed. Note that the data is not hashed.

• Request identifier to be passed to reportSignature.

• The DER encoding of a X.509 certificate. The extension must sign digest using the associated private key.

• The digest that must be signed.

• Refers to the hash algorithm that was used to create digest.

• The unique ID to be used by the extension should it need to call a method that requires it, e.g. requestPin.

• The error template. If present it is displayed to user. Intended to contain the reason for stopping the flow if it was caused by an error, e.g. MAX_ATTEMPTS_EXCEEDED.

• The ID given by Chrome in SignRequest.

chrome.certificateProvider.reportSignature(
  details: ReportSignatureDetails,
): Promise<void>

Should be called as a response to onSignatureRequested.

The extension must eventually call this function for every onSignatureRequested event; the API implementation will stop waiting for this call after some time and respond with a timeout error when this function is called.

chrome.certificateProvider.requestPin(
  details: RequestPinDetails,
): Promise<PinResponseDetails | undefined>

Requests the PIN from the user. Only one ongoing request at a time is allowed. The requests issued while another flow is ongoing are rejected. It's the extension's responsibility to try again later if another flow is in progress.

• Contains the details about the requested dialog.

chrome.certificateProvider.setCertificates(
  details: SetCertificatesDetails,
): Promise<void>

Sets a list of certificates to use in the browser.

The extension should call this function after initialization and on every change in the set of currently available certificates. The extension should also call this function in response to onCertificatesUpdateRequested every time this event is received.

• The certificates to set. Invalid certificates will be ignored.

chrome.certificateProvider.stopPinRequest(
  details: StopPinRequestDetails,
): Promise<void>

Stops the pin request started by the requestPin function.

• Contains the details about the reason for stopping the request flow.

chrome.certificateProvider.onCertificatesUpdateRequested.addListener(
  callback: function,
)

This event fires if the certificates set via setCertificates are insufficient or the browser requests updated information. The extension must call setCertificates with the updated list of certificates and the received certificatesRequestId.

chrome.certificateProvider.onSignatureRequested.addListener(
  callback: function,
)

This event fires every time the browser needs to sign a message using a certificate provided by this extension via setCertificates.

The extension must sign the input data from request using the appropriate algorithm and private key and return it by calling reportSignature with the received signRequestId.

• The callback parameter looks like:

  (request: SignatureRequest) => void

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-11 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-11 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4