From a520d32de7b36b37dc869433dde31c5786f54356 Mon Sep 17 00:00:00 2001 From: Martin Mares Date: Wed, 6 Sep 2017 23:15:46 +0200 Subject: [PATCH] Doc: Explain temp token validity --- client/subauth.1.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/client/subauth.1.txt b/client/subauth.1.txt index 23edea5..6bb6604 100644 --- a/client/subauth.1.txt +++ b/client/subauth.1.txt @@ -46,10 +46,11 @@ not be available in all zones. to have it removed. * *Temporary token:* this is a randomly generated cryptographically signed string, - allowing access to the given user in the given zone for a limited time. This + allowing access to the given user in the given zone for a limited time. Temporary tokens can be useful for services which are used so scarcely that it does not make sense to remember permanent credentials of any kind. Use *subauth --temp-token* - to obtain a temporary token. + to obtain a temporary token. You can set how long will the token be valid + up to a limit configured by the administrator for the given zone. The sub-accounts are managed by the *subauthd*(8) daemon. The *subauth*(1) command is a front-end to this daemon, through which -- 2.39.2