Signature Properties Dialog
Used to inspect the definition and state of the selected signature.
|View Signer's Certificate icon||Opens a viewer for reviewing the certificate information.|
|Certificates||The certificate the signer selected when signing the file.|
|Signer||The Signer defaults to the current user’s login name. This could also be some code or identifier that is meaningful within an organization. This is useful for identifying the signer, especially if the certificate name is different from the signer’s real name.|
|Location||The Location defaults to the current user’s computer name. This could also be some location code, building name, or other identifier that is meaningful within an organization.|
|Purpose||This field could be used to describe the signer’s intent and is normally be a phrase or code that is meaningful within the organization or project.|
|Date||Date and time the file was signed|
|Scope||Indicates the type and extent of signature: model, hidden model, or file. A model signature includes the contents of just one model. A hidden model signature is a model signature that is not displayed. A file signature includes the contents of all models in the file, plus file-level information. The Scope field does not indicate if the signature includes references or not.|
|Prereqs||If yes, this signature depends on other signature.|
|References||If yes, the signature includes the content of attached references.|
|Trusted||If yes, the signature is based on a certificate that is trusted. A certificate is trusted if it was issued by a trusted CA and is not expired.|
|Verified||If yes, the user can be sure that no data in the scope of the signature has changed.|
|Expiry|| Date the signature expires if an expiration date was set upon signing.
This is not the same as expiry date on the underlying digital certificate. A signature does not have to have an expiry date, while a certificate always does. Normally, a signature will remain valid long after the certificate on which it was based has expired.