Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc] Highlight that user must be logged in before token generation #3599

Merged
merged 1 commit into from
Feb 16, 2022
Merged

[doc] Highlight that user must be logged in before token generation #3599

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/web/authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -446,8 +446,11 @@ Command line clients can authenticate itself using the username/password stored
in the [`.codechecker.passwords.json`](#preconfigured-credentials). It is
obviously not a good idea to store passwords in text files. Instead of this the
user is able to generate a token from command line, that can be used to
authenticate in the name of his/her name. To generate a new token, the user must
be logged in first.
authenticate in the name of his/her name.

**Note**: To generate a new token, the user **must be logged in** first. Use
the `CodeChecker cmd login` command for it. After you have successfully logged
in you can generate a new token with the `CodeChecker cmd token new` command.

Personal tokens can be written instead of the user's password in the
`~/.codechecker.passwords.json` file:
Expand Down