If the server you are attempting to contact requires authentication, you will need to supply a username and password. The username should be added in front of the server name with an @ character in between. You will then be prompted to enter a password.
movedat firstname.lastname@example.org:/path/downloadme /local/destination
You may also specify the password on the command line by adding a colon after the username.
movedat user:email@example.com:/path/downloadme /local/destination
This is useful in scripts, but is not generally recommended as it could allow your password to be viewed by other persons using your system. Instead, it is recommended that you use the Password Storage method below when preparing for scripts.
movedat will not prompt for a password if the terminal is non-interactive. For example, if it is run within a script and the password cannot be found in the cache or on the command line, movedat will fail immediately with an authentication error.
The username and password are always encrypted when communicating with the server, even when content encryption is not enabled.
Usernames and passwords must be less than 32 characters, or the limit imposed by the server operating system, whichever is less.
Usernames and passwords should consist of only ASCII letters, numbers, and printable symbols. The use of other characters, such as extended unicode characters, may work in some environments but is not assured and may compromise security.
If the server is running on a Windows system with Active Directory or LDAP enabled, you may specify an authentication domain by using the "-W" option. For example:
movedat -W domain firstname.lastname@example.org:/path/downloadme /local/destination
Non-windows servers will interpret this as a username in the form "username@domain", which may or may not make sense to the operating system.
movedat will store the password for each combination of username, host IP address, and port number so that you do not need to retype it every time. The cached password remains valid for four hours or until it generates an authentication error.
Passwords are automatically cached only when a transaction succeeds.
The password is encrypted prior to storage for security. You may disable password caching by using the -C option or the NoPWCache configuration variable.
In unix systems, the password cache is $HOME/.dei-pwcache1. In Windows, it is %APPDATA%\DEI\dei-pwcache1.dat. You may reset the cache by deleting this file.
The contents of the password cache are encrypted. To view a list of currently cached credentials, enable diagnostics with " -d 1 " in any authenticated movedat command. For example:
# movedat -d 1 email@example.com: Seeking /Users/me/.dei-pwcache1 Cached firstname.lastname@example.org:8080 PERMANENT Expired email@example.com:8080 Password for firstname.lastname@example.org: Caching password for email@example.com:8080
Passwords may be permanently stored in the dei-pwcache1 file. This is useful for scripts or frequently accessed servers.
Use the -A command line option to add to a set of credentials to storage:
movedat [-p port] -A user[:password]@example.com:
If you do not specify a port, the default 8080 will be assumed. If you do not specify a password, you will be prompted for one. For example:
movedat -A firstname.lastname@example.org:
If you wish to expire and remove credentials, including those cached temporarily, use the -E command line option:
movedat [-p port] -E email@example.com:
Note that the username, port number, and server must match for the credentials to be used. If the server returns a Bad Credentials error, the entry will be automatically removed from the cache!