public class PKIXCertPathBuilderResult extends PKIXCertPathValidatorResult implements CertPathBuilderResult
PKIXCertPathBuilderResult are returned by
build method of
objects implementing the PKIX algorithm.
PKIXCertPathBuilderResult objects contain the
certification path constructed by the build algorithm, the
valid policy tree and subject public key resulting from the build
algorithm, and a
TrustAnchor describing the certification
authority (CA) that served as a trust anchor for the certification path.
Unless otherwise specified, the methods defined in this class are not thread-safe. Multiple threads that need to access a single object concurrently should synchronize amongst themselves and provide the necessary locking. Multiple threads each manipulating separate objects need not synchronize.
|Constructor and Description|
Creates an instance of
|Modifier and Type||Method and Description|
Returns the built and validated certification path.
Return a printable representation of this
clone, getPolicyTree, getPublicKey, getTrustAnchor
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
public PKIXCertPathBuilderResult(CertPath certPath, TrustAnchor trustAnchor, PolicyNode policyTree, PublicKey subjectPublicKey)
PKIXCertPathBuilderResultcontaining the specified parameters.
certPath- the validated
TrustAnchordescribing the CA that served as a trust anchor for the certification path
policyTree- the immutable valid policy tree, or
nullif there are no valid policies
subjectPublicKey- the public key of the subject
NullPointerException- if the
public CertPath getCertPath()
CertPathobject does not include the trust anchor. Instead, use the
getTrustAnchor()method to obtain the
TrustAnchorthat served as the trust anchor for the certification path.
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2013, Oracle and/or its affiliates. All rights reserved.