ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-02-20 17:33:15 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update key-concepts-identity.rst (#3480)

Browse Source
This commit is contained in:
Joel Dudley 2018-06-29 16:31:48 +01:00 committed by GitHub
parent 2b6018f050
commit 6d77d045e8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/source/key-concepts-identity.rst
View File

@ -10,13 +10,17 @@ Identity
Identities in Corda can represent:
* Legal identity of an organisation
* Service identity of a network service
* The legal identity of an organisation
* The service identity of a network service
Legal identities are used for parties in a transaction, such as the owner of a cash state. Service identities are used
for those providing transaction-related services, such as notary, or oracle. Service identities are distinct to legal
identities so that distributed services can exist on nodes owned by different organisations. Such distributed service
identities are based on ``CompositeKeys``, which describe the valid sets of signers for a signature from the service.
These identities are distinct from the RPC users that are able to connect to the node via RPC.
Identity types
--------------
Whereas legal identities are used to represent parties in transactions, such as the owner of a cash state, service identities
are used for entities providing transaction-related services, such as notaries or oracles. Service identities are distinct
from legal identities so that distributed services can exist on nodes owned by different organisations. Such distributed service identities are based on ``CompositeKeys``, which describe the valid sets of signers for a signature from the service.
See :doc:`api-core-types` for more technical detail on composite keys.
Identities are either well known or confidential, depending on whether their X.509 certificate (and corresponding
@ -55,4 +59,4 @@ business sensitive details of transactions). In some cases nodes may also use pr
to the main network map service, for operational reasons. Identities registered with such network maps must be
considered well known, and it is never appropriate to store confidential identities in a central directory without
controls applied at the record level to ensure only those who require access to an identity can retrieve its
certificate.
certificate.