chromex.app.platform-keys — binaryage/chromex 0.6.5

clj

Use the chrome.platformKeys API to access client certificates managed by the platform. If the user or policy grants the permission, an extension can use such a certficate in its custom authentication protocol. E.g. this allows usage of platform managed certificates in third party VPNs (see 'vpnProvider chrome.vpnProvider').

• available since Chrome 45
• https://developer.chrome.com/apps/platformKeys

api-table clj

gen-call clj

gen-wrap clj/s macro

(gen-wrap kind item-id config & args)

get-key-pair clj/s macro

(get-key-pair certificate parameters)

Passes the key pair of certificate for usage with 'platformKeys.subtleCrypto' to callback.

|certificate| - The certificate of a 'Match' returned by 'selectClientCertificates'. |parameters| - Determines signature/hash algorithm parameters additionally to the parameters fixed by the key itself. The same parameters are accepted as by WebCrypto's importKey function, e.g. RsaHashedImportParams for a RSASSA-PKCS1-v1_5 key. For RSASSA-PKCS1-v1_5 keys, additionally the parameters { 'hash': { 'name': 'none' } } are supported. The sign function will then apply PKCS#1 v1.5 padding and but not hash the given data. Currently, this function only supports the 'RSASSA-PKCS1-v1_5' algorithm with one of the hashing algorithms 'none', 'SHA-1', 'SHA-256', 'SHA-384', and 'SHA-512'.

This function returns a core.async channel of type promise-chan which eventually receives a result value. Signature of the result value put on the channel is [public-key private-key] where:

|public-key| - https://developer.chrome.com/apps/platformKeys#property-callback-publicKey. |private-key| - Might be null if this extension does not have access to it.

In case of an error the channel closes without receiving any value and relevant error object can be obtained via chromex.error/get-last-error.

https://developer.chrome.com/apps/platformKeys#method-getKeyPair.

get-key-pair* cljs

(get-key-pair* config certificate parameters)

select-client-certificates clj/s macro

(select-client-certificates details)

This function filters from a list of client certificates the ones that are known to the platform, match request and for which the extension has permission to access the certificate and its private key. If interactive is true, the user is presented a dialog where they can select from matching certificates and grant the extension access to the certificate. The selected/filtered client certificates will be passed to callback.

|details| - https://developer.chrome.com/apps/platformKeys#property-selectClientCertificates-details.

This function returns a core.async channel of type promise-chan which eventually receives a result value. Signature of the result value put on the channel is [matches] where:

|matches| - The list of certificates that match the request, that the extension has permission for and, if interactive is true, that were selected by the user.

In case of an error the channel closes without receiving any value and relevant error object can be obtained via chromex.error/get-last-error.

https://developer.chrome.com/apps/platformKeys#method-selectClientCertificates.

select-client-certificates* cljs

(select-client-certificates* config details)

subtle-crypto clj/s macro

(subtle-crypto)

An implementation of WebCrypto's SubtleCrypto that allows crypto operations on keys of client certificates that are available to this extension.

https://developer.chrome.com/apps/platformKeys#method-subtleCrypto.

subtle-crypto* cljs

(subtle-crypto* config)

tap-all-events clj/s macro

(tap-all-events chan)

Taps all valid non-deprecated events in chromex.app.platform-keys namespace.

verify-tls-server-certificate clj/s macro

(verify-tls-server-certificate details)

Checks whether details.serverCertificateChain can be trusted for details.hostname according to the trust settings of the platform. Note: The actual behavior of the trust verification is not fully specified and might change in the future. The API implementation verifies certificate expiration, validates the certification path and checks trust by a known CA. The implementation is supposed to respect the EKU serverAuth and to support subject alternative names.

|details| - https://developer.chrome.com/apps/platformKeys#property-verifyTLSServerCertificate-details.

This function returns a core.async channel of type promise-chan which eventually receives a result value. Signature of the result value put on the channel is [result] where:

|result| - https://developer.chrome.com/apps/platformKeys#property-callback-result.

In case of an error the channel closes without receiving any value and relevant error object can be obtained via chromex.error/get-last-error.

https://developer.chrome.com/apps/platformKeys#method-verifyTLSServerCertificate.

verify-tls-server-certificate* cljs

(verify-tls-server-certificate* config details)