Fabian Grünbichler 28e3dc05e2 API token: add REs, helpers, parsing + writing ... token definitions/references in user.cfg always use the full form of the token id, consisting of: USER@REALM!TOKENID token definitions are represented by their own lines prefixed with 'token', which need to come after the corresponding user definition, but before any ACLs referencing them. parsed representation in a user config hash is inside a new 'tokens' element of the corresponding user object, using the unique-per-user token id as key. only token metadata is stored inside user.cfg / accessible via the parsed user config hash. the actual token values will be stored root-readable only in a separate (shadow) file. 'comment' and 'expire' have the same semantics as for users. 'privsep' determines whether an API token gets the full privileges of the corresponding user, or just the intersection of privileges of the corresponding user and those of the API token itself. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>		2020-01-28 20:59:36 +01:00
..
API2	API: add group members to group index	2020-01-28 20:56:55 +01:00
Auth	auth: pull username REs into variables	2020-01-14 12:28:13 +01:00
CLI	pveum: add list commands	2019-11-23 17:42:51 +01:00
AccessControl.pm	API token: add REs, helpers, parsing + writing	2020-01-28 20:59:36 +01:00
Makefile	convert pveum into a PVE::CLI class	2015-10-01 16:49:37 +02:00
RPCEnvironment.pm	rpcenv: drop unused roles()	2020-01-14 12:24:04 +01:00