CertChain React Native Reference Documentation

CertChain

Current Version: 11.6.1

Chilkat.CertChain

Inspect, verify, export, and work with X.509 certificate chains.

Chilkat.CertChain is a compact helper class for representing and working with X.509 certificate chains. It lets applications inspect the ordered certificates in a chain, retrieve individual certificates, determine whether the chain reaches a root, check for expired certificates, verify chain signatures, test whether the root is trusted, load certificate chains from JWK x5c data, and export the chain as X509PKIPathv1.

Chain inspection

Examine the certificates in chain order and retrieve individual certificates with CertAt.

Root and trust checks

Determine whether the chain reaches a root certificate and whether that root is trusted.

Signature verification

Verify that each certificate in the chain is signed by the next certificate in the chain.

Expiration checks

Detect whether one or more certificates in the chain are expired.

JWK x5c support

Load certificate chains from JWK x5c arrays used by JWT, JWS, and other security-token workflows.

Chain export

Export the certificate chain in X509PKIPathv1 format when that representation is required.

Common pattern: Use CertChain to reason about the chain as a whole. For certificate-level details such as subject, issuer, SAN values, key usage, validity dates, fingerprints, serial numbers, and extensions, retrieve each certificate with CertAt and inspect it using Chilkat.Cert.

For an extended overview, see CertChain Class Overview.

Object Creation

// npm install @chilkat/react-native react-native-nitro-modules
// (React Native 0.76+ with the New Architecture; then `pod install` for iOS.  The Chilkat
//  native library is downloaded and verified during the native build -- see the package README.)

import { Chilkat, CertChain } from '@chilkat/react-native'

// Once per app start, before any other Chilkat call:
Chilkat.unlockBundle('Anything for 30-day trial')   // shorthand for new Global().unlockBundle(..)

const certChain = new CertChain()
// ... the native object is released when `certChain` is garbage collected, or now with certChain.dispose()

new CertChain()

Creates the underlying native Chilkat object. CertChain is a Nitro Module HybridObject: use it from the JavaScript thread only (it cannot be passed to a Worklet or another runtime). Every member is synchronous and blocks the JavaScript thread until Chilkat returns; a method that can take a while also exists as a ...Async twin returning a Promise, which runs the same call on a native worker thread so the UI keeps rendering. While such a call is pending, every other call on this object throws, except abort() and assigning onPercentDone / onProgressInfo.

dispose(): void

Releases the native object immediately instead of waiting for garbage collection (useful for a large BinData or an open socket). Calling it more than once is harmless; any other use of the object afterwards throws. An object with a pending ...Async call cannot be disposed until the promise settles.

Errors

A method that can fail throws a plain Error: a method whose only outcome is success or failure returns void and throws on failure; a method producing a string or an object returns it and throws where Chilkat would have returned null. The error's message is "Class.method(...): reason", where the reason is the last informative line of the object's lastErrorText, which holds the full Chilkat log of the failed call. A ...Async twin rejects its promise with the same Error instead of throwing. Properties never throw, and methods that answer a question (has..., is..., ...) return a plain boolean.

try {
  certChain.someMethod(...)
} catch (e) {
  console.log((e as Error).message)   // CertChain.someMethod(...): <reason>
  console.log(certChain.lastErrorText)   // the full Chilkat log of the failed call
}

// The same call without blocking the JavaScript thread:
try {
  await certChain.someMethodAsync(...)
} catch (e) {
  console.log((e as Error).message)   // CertChain.someMethodAsync: <reason>
}

Properties

DebugLogFilePath

// read/write
debugLogFilePath: string

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

A timeout property set to 0, indicating an infinite timeout.
A hang occurring within an event callback in the application code.
An internal bug in the Chilkat code causing the hang.

More Information and Examples

Index	Meaning
`0`	The target or end-entity certificate—the certificate farthest from the root end of the chain
`1 ... NumCerts - 2`	Intermediate CA certificates, when present
`NumCerts - 1`	The highest certificate available in the chain

Index	Position in the chain
`0`	Target or end-entity certificate
`1 ... NumCerts - 2`	Intermediate CA certificates, when present
`NumCerts - 1`	Highest certificate available in the chain; a root certificate only when `ReachesRoot` is `true`

Representation	Certificate order
`CertChain` indexing	Target/leaf → intermediates → root
`X509PKIPathv1`	Root → intermediates → target/leaf

CertChain React Native Reference Documentation

CertChain

Current Version: 11.6.1

Inspect, verify, export, and work with X.509 certificate chains.

Chain inspection

Root and trust checks

Signature verification

Expiration checks

JWK x5c support

Chain export

Object Creation

Errors

Properties

DebugLogFilePath

LastErrorHtml

LastErrorText

LastErrorXml

LastMethodSuccess

NumCerts

NumExpiredCerts

ReachesRoot

UncommonOptions

VerboseLogging

Version

Methods

CertAt

IsRootTrusted

LoadX5C

VerifyCertSignatures

X509PKIPathv1