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

Jump to bottom

Add a ref to the API token creation docs #77

Merged
merged 1 commit into from
Sep 14, 2023
Merged

Add a ref to the API token creation docs #77

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
3 changes: 3 additions & 0 deletions docs/config.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,6 +255,8 @@ Jira server, and jipdate supports password based authentication, as well as
token based. Using token authentication is considered more secure than
password. The `server` configuration must include at least an `url` attribute. A
`token` attribute can be added optionally.
To create an API token, follow the procedure described in the `Atlassian
documentation`_.

When the `token` attribute is present, Jipdate will use token based
authentication. Otherwise, it will use password based authentication.
Expand Down Expand Up @@ -294,3 +296,4 @@ stored here, then jipdate won't ask for it when running the script.


.. _YAML format: https://yaml.org/spec/1.2/spec.html
.. _Atlassian documentation: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/#Create-an-API-token
Loading