Node:Mingle init, Next:RSA key distribution, Previous:Mingle single sign-on, Up:Beginning to use Mingle
After Mingle sign-on, you are uniquely identified as your Mingle ID in
the corresponding cluster. However, if you wish to index files on a
host or specify access control decisions, you will need to let the
corresponding Mingle server know which local user you are via the
mingle init command. This Mingle init process also presents your
Mingle ID to the server so that the server can sign the request on your
behalf before forwarding the request to the remote servers. Note that
the mingle init request has to be submitted locally, meaning that
you will need to log in to the desired Mingle host and submit a request
there.
The syntax of the mingle init request is the following:
mingle init mingle-id
where mingle-id is the Mingle ID that you have signed on. Next,
the Mingle server interactively prompts you for your Mingle password for
authentication, creates an entry for you, and associate your local user
name and your Mingle ID together so that you no longer need to enter
your Mingle ID for subsequent requests. The local Mingle server will
also fetch your RSA private signing key from the master server using
your password and cache it (see RSA key distribution).
After the cached private key expires, this Mingle init process can be repeated to obtain a refresh copy of key for caching. Therefore, the private key cache expiration time determines the frequency of executing such "init" command. Modify the parameter "PrivateTTL" to adjust the expiration time of caching private keys.
After Mingle init, use the command mingle display to check your
current status. For example, if your local user name is bovik and
your Mingle ID is mbovik, then
mingle display
will return
Mingle ID = mbovik Local user ID = bovik