
#JIRA CLIENT BASED VIEW PASSWORD#
Password-based API authentication works for self-hosted Jira only, and has been deprecated for users of Atlassian Cloud.ĭepending on your version of Jira, either of the above token authentication examples may be used, substituting a user's password for a generated token.
#JIRA CLIENT BASED VIEW HOW TO#
See examples/bearerauth for how to use the Bearer authentication scheme with Jira in Go. PATs use the Bearer authentication scheme. Similar to the API tokens, PATs are a safe alternative to using username and password for authentication with scripts and integrations. } Bearer - Personal Access Tokens (self-hosted Jira)įor self-hosted Jira (v8.14 and later), Personal Access Tokens (PATs) were introduced. Additional information about Atlassian Cloud API tokens can be found here.Ī more thorough, runnable example is provided in the examples directory.Ĭlient, err := jira.

You can generate a token for your user here. Token-based authentication uses the basic authentication scheme, with a user-generated API token in place of a user's password. That client can then be passed into the NewClient function when creating a jira client.įor convenience, capability for basic and cookie-based authentication is included in the main library. Instead, authentication should be handled withinĪn http.Client. The go-jira library does not handle most authentication directly. MESOS-3325: Running in a container causes slave to be lost after a restart // Type: Bug // Priority: Critical Note that we also run our tests against 1.13, though only the last two versions For all possible API endpoints of Jira have a look at latest Jira REST API documentation. See Call a not implemented API endpoint how to do this. This package is not Jira API complete (yet), but you can call every API endpoint you want.

Call every API endpoint of the Jira, even if it is not directly implemented in this library.Create and retrieve issue transitions (status updates).Authentication (HTTP Basic, OAuth, Session Cookie, Bearer (for PATs)).If you want to stay more stable, please use v1.* - See our releases.

See our milestone Road to v2 and provide feedback in Development is kicking: Road to v2 🚀 #489.Īttention: The current main branch represents the v2 development version - we treat this version as unstable and breaking changes are expected. remove flaws introduced during the early times of this library.being compliant with different kinds of Atlassian Jira products (on-premise vs.v2 will contain breaking changes ⚠️ The current main branch can contains the development version of v2.
