| Class | Description |
|---|---|
| AbstractParty |
An
class AbstractParty contains the common elements of class Party and class AnonymousParty, specifically the owning key of
the party. In most cases class Party or class AnonymousParty should be used, depending on use-case. |
| AnonymousParty |
The
class AnonymousParty class contains enough information to uniquely identify a class Party while excluding private
information such as name. It is intended to represent a party on the distributed ledger. |
| CordaX500Name |
X.500 distinguished name data type customised to how Corda uses names. This restricts the attributes to those Corda
supports, and requires that organisation, locality and country attributes are specified. See also RFC 4519 for
the underlying attribute type definitions
|
| IdentityUtils | |
| Party |
The
class Party class represents an entity on the network, which is typically identified by a legal name and public key
that it can sign transactions under. As parties may use multiple keys for signing and, for example, have offline backup
keys, the "public key" of a party can be represented by a composite construct – a class CompositeKey, which combines multiple
cryptographic public key primitives into a tree structure. |
| PartyAndCertificate |
A full party plus the X.509 certificate and path linking the party back to a trust root. Equality of
class PartyAndCertificate instances is based on the party only, as certificate and path are data associated with the party,
not part of the identifier themselves. |