Account Repositories
An Account Repository is a container for organizing and managing Accounts, which store authentication credentials used by the USP Server to validate external incoming connections, such as those from partners, customers, vendors, internal users, or other organizations that exchange files with your system.
Before You Begin
Integration with Rules
Account Repositories integrate with Rules, allowing the USP Server to validate inbound client connections against a defined set of Accounts. This integration enables flexible, centralized management of client authentication without requiring individual credential management at each connection point.
Inbound Authentication Setup
To configure an Account Repository (and its associated Accounts) as the authentication source for inbound connections, follow these steps:
- In the Rule's configuration, set the Inbound Authentication Source to Account Repository.
- Select the appropriate Account Repository from the dropdown menu.
For more information, refer to Rules.
Authentication Flow
Once a Rule is configured to use an Account Repository, the following sequence occurs during an inbound connection:
- An Account attempts to connect to the USP Server.
- The incoming connection is processed by an Inbound Node.
- The USP Server consults the configured Account Repository to validate the credentials.
- If a matching Account (by username) is found, credentials are validated according to the SSH Authentication Method defined in the Rule.
Account Repository Administration via USP Admin UI
Adding an Account Repository
To add an Account Repository, follow these steps:
- From the Sidebar, click Configuration > Accounts.
- Click Add Account Repository.
- Complete the details for the new Account Repository using the Field Descriptions table as a guide.
- Click Save.
Field Descriptions
| Name | Description | Specifications | Required |
|---|---|---|---|
| Name | The name of the Account Repository. | Must be unique. | Yes |
| Description | The description of the Account Repository. | No |
Editing an Account Repository
To edit an Account Repository, follow these steps:
- From the Sidebar, click Configuration > Accounts.
- Click the Name of the Account Repository you want to edit.
- Click the Edit button above the Account Repository details.
- Edit the Account Repository details using the Field Descriptions table as a guide.
- Click Save.
If you modify an Account Repository that is currently in use by a USP Server instance, the changes will not take effect until you manually apply the updated configuration by pushing it to the server. To apply the changes:
- Navigate to Monitoring > Status.
- Click the Name of the associated USP Server instance.
- Go to the Configuration tab.
- Review the pending changes in the Updated Configuration column.
- If the changes are correct, click Push Configuration.
Account Repository details include all parameters given in the Field Descriptions table above, plus the following read-only metadata:
Account Repository Metadata
| Name | Description |
|---|---|
| ID | Universally Unique Identifier of this Account Repository. |
| Created At | Date and time this Account Repository was created. |
| Updated At | Date and time this Account Repository was last updated. |
Deleting an Account Repository
To delete an Account Repository, follow these steps:
- From the Sidebar, click Configuration > Accounts.
- Click the Name of the Account Repository you want to delete.
- Click the Delete button above the Account Repository details.
- You will be asked to confirm the deletion. Click Delete.
USP Manager prevents deletion of an Account Repository if it is currently referenced by a Rule.
Additionally, if the Account Repository is used by a USP Server instance, the updated configuration must be manually applied. To apply the changes:
- Navigate to Monitoring > Status.
- Click the Name of the associated USP Server instance.
- Go to the Configuration tab.
- Review the pending changes in the Candidate Configuration - Preview section.
- If the changes are correct, click Push Configuration.
The changes do not take effect on the server until this step is completed.