Open topic with navigation

# PutDigitalSafe

Indexes documents into Digital Safe through the Digital Safe REST API.

## Properties

Name | Default Value | Description
--- | --- | ---
Proxy Configuration Service |  | A ProxyConfigurationService that specifies the proxy server to use.
Document Registry Service |  | A DocumentRegistryService that manages and updates a document registry database. This ensures that documents are indexed in the correct order. For more information about the document registry service, see Index Documents in the Correct Sequence.
OAuth Database Service |  | A DatabaseService to use to store OAuth tokens in an external database. This is necessary if you want to use the PutDigitalSafe processor on a NiFi cluster. For information about creating the database service, see Create a Database Service.
DigitalSafe base URL | http://localhost/ | The base URL of the Digital Safe. The following URL must be valid, where `DigitalSafeURL/` is replaced by the value of this parameter:
    DigitalSafeURL/rest-api/documents/v1/
Client ID |  | The OAuth application key (client ID) to use to authenticate with Digital Safe.
Client secret |  | The OAuth application secret (client secret) to use to authenticate with Digital Safe.
Refresh token |  | The OAuth refresh token to use to authenticate with Digital Safe.
Sender | admin@testdomain1.digitalsafe.net | To insert binary files into Digital Safe, the processor inserts an e-mail message (.eml) file with the binary file as an attachment. This parameter specifies the e-mail address that the e-mail message appears to have been sent from.
Recipient | admin@testdomain1.digitalsafe.net | To insert binary files into Digital Safe, the processor inserts an e-mail message (.eml) file with the binary file as an attachment. This parameter specifies the e-mail address that the e-mail message appears to have been sent to.
Username |  | The user name to use to authenticate with Digital Safe. This user name is associated with the OAuth settings that you provide.
Disable metadata encoding regex |  | To prevent the processor from encoding some metadata fields using RFC1522, use this parameter to identify the fields. This parameter accepts a regular expression. If the name of a field matches the regular expression, the field value is not encoded with RFC1522.

## Relationships

Name | Description
--- | ---
success | FlowFiles that were indexed successfully.
failure | FlowFiles that were not indexed successfully.

© Copyright 2018-2019 Micro Focus or one of its affiliates | Send documentation feedback Close Send documentation feedback To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to swpdl.idoldocsfeedback@microfocus.com. We appreciate your feedback! Product: Topic Title: Help Topic: Feedback:

_FT_HTML5_bannerTitle.htm