Functional overview
As a user
in my preferences, I have a section "API Keys" where I can
- Generate a new key with a description
This key will be a random string and is displayed only once at generation.
Bellow the key generation I have a table that lists all the keys already generated with their description, creation date, last used date and last used IP address + action to revoke (delete) key.
API key is made with prefixed with 'tlp-k1-' for audit purpose.
A key can only be used for REST accesses.
As a REST api user
I can use the generated API key in my REST call headers:
curl -H 'X-Auth-AccessKey: stuff' https://tuleap.example.com/...
When using API Key there is no need to generate a token to access the REST API.
While tokens remains accessible, the documentation of the route and the documentation of Tuleap is updated to inform people about API keys being the prefered way to access the API.
Technical overview
Ensure that 'last_access_date' for corresponding user is properly updated when using API key instead of tokens