Version 3 has been released!

{AUTH?} command (Request token to be presented)

The {AUTH?} requests that the other computer present some type of token via an {AUTH} command.


{AUTH?} type  prompt  style ␑ cache

  • type - type of token, for example:
    • R = Registration token
    • S = Server token
    • W = Write permission
    • HOST = Network host name to use (ESP device only)
    • userdefined = any token name
  • prompt - indicate if the user should be prompted (if technically possible)
    • empty or 0 = none
    • 1 = ask for token
  • style - how the token is to be encoded in the {AUTH} command
    • empty or 0 = internal algorithm
    • 1 = send it as plain text
    • 2 = SHA1(ID+token) with hyphens after every 8 characters
  • cache - indicate if the token should be cached for future sessions
    • empty or 0 = don't store
    • 1 = store it
  • Using a user prompt can be used to solicit a 'password' type token.
  • Keep in mind that not all RemoteSigns can solicit input from a user.
  • User defined token namespace can be freely used with the understanding that future RemoteSign development may introduce new internal tokens in the same namespace.

See also: {TOKEN} {AUTH}

Overview and list of all RemoteSign commands: API reference

Supported by:
RemoteSign Windows v3.6 (any type)
RemoteSign Sequencer v3.5 (send)
RemoteSign ESP v3.5 (types R and S)
Arrivals & Departures v2.1 (type R)