| name | data type | type | namespace | min/max occurs | description |
|---|---|---|---|---|---|
| digest | base64Binary | element | 0/1 | ||
Properties inherited from edcPki |
|||||
| id | long | element | 1/1 | ||
| certificate | string | element | 0/1 | ||
| accountId | long | element | 1/1 | ||
| version | int | element | 1/1 | ||
| serial | string | element | 0/1 | ||
| algorithm | string | element | 0/1 | ||
| subject | string | element | 0/1 | ||
| issuer | string | element | 0/1 | ||
| notBefore | dateTime | element | 0/1 | ||
| notAfter | dateTime | element | 0/1 | ||
| createdOn | dateTime | element | 0/1 | ||
| createdBy | long | element | 1/1 | ||
| modifiedOn | dateTime | element | 0/1 | ||
| modifiedBy | long | element | 1/1 | ||
| name | string | element | 0/1 | ||
| optlock | int | element | 1/1 | The optlock field is used to detect that this entity has not been
modified by someone else. When updating an entity, first do a find to
get the latest version of the entity and note the value of the optlock.
Then in the update operation, set the optlock value to match the value
that you found. If someone else has updated the entity between your
find and update operations, the update will fail and the db/server will
return an error.
See this stackoverflow question for more information on optimistic locking. |
|
Example
<BlockedCertificate> <digest>...</digest> <id>...</id> <certificate>...</certificate> <accountId>...</accountId> <version>...</version> <serial>...</serial> <algorithm>...</algorithm> <subject>...</subject> <issuer>...</issuer> <notBefore>...</notBefore> <notAfter>...</notAfter> <createdOn>...</createdOn> <createdBy>...</createdBy> <modifiedOn>...</modifiedOn> <modifiedBy>...</modifiedBy> <name>...</name> <optlock>...</optlock> </BlockedCertificate>