<?xml version="1.0"?>
<doc>
    <assembly>
        <name>Lacuna.RestPki.Api</name>
    </assembly>
    <members>
        <member name="P:Lacuna.RestPki.Api.CadesSignature.CadesSignaturePostRequestBase.EncapsulateContent">
            <summary>
            Optionally denotes whether the resulting CMS should include the content signed. If ommitted, the following rules apply:
            - If no CmsToSign is given, the resulting CMS will include the content
            - If a CmsToCoSign is given, the resulting CMS will include the content if and only if the CmsToCoSign also includes the content
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.CertificateSummary.Thumbprint">
            <summary>
            SHA-1 thumbprint of the certificate (hex encoded)
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.CertificateSummary.ThumbprintSHA256">
            <summary>
            SHA-256 thumbprint of the certificate (hex encoded)
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.CertificateSummary.SubjectCommonName">
            <summary>
            The CN= part of the subject name
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.CertificateSummary.SubjectDisplayName">
            <summary>
            Name of the subject, i.e., of the individual to which the certificate was issued (see remarks to understand differences to `SubjectCommonName`)
            </summary>
            <remarks>
            In certain certificates, the CN field of the subject name is known to carry extra information that is not actually part of the
            subject's name, for instance in Brazilian certificates which have a *:CPF* suffix. The CN field may not even not contain the subject's
            name at all, as is the case with Brazilian company certificates, which have the company name on the CN field, intead of the name of the
            responsible individual. In such cases, this property may differ from `SubjectCommonName`.
            
            This property should be preferred if the intention is to get the actual name of the individual to which the certificate was issued,
            not necessarily what the CN= field states.
            </remarks>
        </member>
        <member name="P:Lacuna.RestPki.Api.CertificateSummary.SubjectIdentifier">
            <summary>
            The identifier of the subject
            </summary>
            <remarks>
            The meaning of this property depends on the certificate:
            
            * PKI Brazil certificates: corresponds to the subject's *CPF* (digits only)
            * For Italian certificates: corresponds to the subject's *codice fiscale*
            * Othewise: null
            
            Please contact us if the certificates in your region contain a relevant field that could be decoded into this property.
            </remarks>
        </member>
        <member name="P:Lacuna.RestPki.Api.CertificateSummary.EmailAddress">
            <summary>
            The subject's email address
            </summary>		
        </member>
        <member name="P:Lacuna.RestPki.Api.CertificateSummary.Organization">
            <summary>
            The organization of the subject
            </summary>
            <remarks>
            The meaning of this property depends on the certificate:
            
            * PKI Brazil company (PJ) certificate: the company name
            * Otherwise: field O= of the subject name, if any
            
            Please contact us if the certificates in your region contain a relevant field that could be decoded into this property.
            </remarks>
        </member>
        <member name="P:Lacuna.RestPki.Api.CertificateSummary.OrganizationIdentifier">
            <summary>
            The subject organization's identifier
            </summary>
            <remarks>
            /// The meaning of this property depends on the certificate:
            
            * PKI Brazil company (PJ) certificate: the company's *CNPJ* (digits only)
            * Otherwise: null
            
            Please contact us if the certificates in your region contain a relevant field that could be decoded into this property.
            </remarks>
        </member>
        <member name="P:Lacuna.RestPki.Api.PadesSignature.PadesVisualPositioningModel.PageNumber">
            <summary>
            Page on which to insert the visual representation. Negative values denote pages counted
            from the end of the document (-1 means last page). Zero denotes that, if no signatures are
            present, a new page should be appended to the document.
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.PadesSignature.PadesVisualTextModel.Text">
            <summary>
            Text to be written on the signature visual representation. The text may contain tags in the format {{tagName}} which will be
            substituted with according values. The supported tags are {{signerName}}, {{signerNationalId}}, {{signerEmail}} and {{issuerCommonName}}.
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.PaginatedRequest.PageIndex">
            <summary>
            The index of the desired page. Starts at 1. If omitted, fetches the first page.
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.PaginatedRequest.PageSize">
            <summary>
            The size of a page. If omitted, the request uses a default size.
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.PaginatedRequest.SortDirection">
            <summary>
            The sort direction (ascending or descending). If omitted, sort order will be descending by default
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.PaginatedRequest.SortField">
            <summary>
            The sort field. 
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.Signature.OpenSignatureRequestModel.AuditPackage">
            <summary>
            Configuration of the audit package generation. Optional, if omitted an audit package will not be generated
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.Signature.OpenSignatureRequestModel.DefaultSignaturePolicyId">
            <summary>
            Default signature policy to be used to validate signature. This value is used to validate signatures without an
            explicit validation policy attribute and also signatures with an explicit validation policy attribute that is not
            among the policies specified in AcceptableExplicitPolicies. In order to accept only a certain list of explicit
            policies, this value should be omitted.
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.Signature.OpenSignatureRequestModel.AcceptableExplicitPolicies">
            <summary>
            List of explicit policies that should be accepted when validating signatures with a explicit validation policy attribute.
            If a signature being validated has an explicit validation policy attribute which is not among the values passed, then the
            policy specified in DefaultSignaturePolicyId is used. In order to accept only the given list of explicit policies, omit
            the value DefaultSignaturePolicyId.
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.Signature.AuditPackageOptions.Generate">
            <summary>
            Whether an audit package zip file should be generated and returned
            </summary>
        </member>
        <member name="P:Lacuna.RestPki.Api.Signature.AuditPackageOptions.IncludeFile">
            <summary>
            Whether to include the signed file on the package
            </summary>
        </member>
        <member name="F:Lacuna.RestPki.Api.StandardSecurityContexts.LacunaTest">
            <summary>
            Lacuna Test PKI (use for development purposes only!) If you are using an on-premises instance of Rest PKI (instead of https://pki.rest/), this security
            context might have to be created first.
            </summary>
        </member>
    </members>
</doc>
