Page Comparison

This enhancement allows the sharing of accounts between servers. It avoids the need for duplicate configuration for FTP and SFTP local servers by having accounts that are shared between local server. (another option would be to allow a server to support multiple protocols)-????

Prior to this change, a local account was only defined for a given local server and it was not possible to have the same account for multiple protocols. For instance, to allow a partner to transfer files over SFTP and FTP, it was required to have both an SFTP and FTP server, each with its own account. Each account was then maintained independently which created additional overhead in configuration and maintenance (password or key updates).

The implementation uses the current Local Account table and a New table for handling authorization.

Be able to list share accounts from server endpoint.

Need to remove the column local_accounts.local_agent_id

local and shared account are functionally the same.

the local command is kept for regression:
- if an account is created with the 'local' command or API, then the local server parameter is mandatory and the association is made in the link table.

- if an account is created with the 'share' command or API, then the account is created without any link and cannot be used until there is at least one explicit association to a local server.

- if an account is linked with more than 1 server then it cannot be deleted from the 'local' command. Return an error mentioning it is a shared account.

• Deprecated LocalAccount -> Local Agent Id
  • Replace by sb_local_account_auth fields (If the server is removed will cascade)

• Accounts will be managed as a separated account and then Assign into the server via the pivot table ? ( Same way for the rules)

• API Changes * POST /api/sb_servers/<server-name>/account
  • Link the account with the server
  • Body { "login": <user-name> }
  • DELETE /api/sb_servers/<server-name>/account
    • Remove Link
• New API Endpoint
  • POST /api/sb_account * Same fields
  • List Account GET /api/sb_account
  • Get Account GET /api/sb_account/<name>
  • Update Account PUT /api/sb_account/<name>
  • Delete Account DELETE /api/sb_account/<name>

• API Endpoints

  Code Block

  ### List Accounts GET http://admin:admin_password@localhost:8080/api/sb_local_accounts ### Create Account POST http://admin:admin_password@localhost:8080/api/sb_local_accounts Content-Type: application/json { "login": "test", "password": "123" } ### Get Account GET http://admin:admin_password@localhost:8080/api/sb_local_accounts/test ### Disable Account PUT http://admin:admin_password@localhost:8080/api/sb_local_accounts/user/disable ### Enable Account PUT http://admin:admin_password@localhost:8080/api/sb_local_accounts/test/enable ### Update Account PATCH http://admin:admin_password@localhost:8080/api/sb_local_accounts/test Content-Type: application/json { "password": "123456" } ### Replace Account PUT http://admin:admin_password@localhost:8080/api/sb_local_accounts/test Content-Type: application/json { "login":"user", "password": "123456" } ### Authorize Account PUT http://admin:admin_password@localhost:8080/api/sb_local_accounts/user/allow/sftp-local-account ### Revoke Account PUT http://admin:admin_password@localhost:8080/api/sb_local_accounts/user/disallow/sftp-local-account ### Delete Account DELETE http://admin:admin_password@localhost:8080/api/sb_local_accounts/user

  
  

This change incorporates license management within Universal Data Mover Gateway. All instances of Universal Data Mover Gateway are now required to have a license key attached to the installation. Universal Data Mover Gateway is licensed by the number of executions per month*; specifically, the number of file transfer instances that completed as DONE over a period of one month. 

is there any distinction in the transfer types? like all count or only incoming vs outgoing? 

To receive and apply your license keys, please follow the below steps and reference UDMG Licensing. 

*should we add a note about how some customers are licensed differently? or have unlimited?; thinking of the ones licensed per partners but theres no system mechanism to track (which we dont want to highlight i assume)