-
Notifications
You must be signed in to change notification settings - Fork 71
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.
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
Support personal token authentication in jira kamelet #1529
Comments
claudio4j
added a commit
to claudio4j/camel-kamelets
that referenced
this issue
Jul 7, 2023
- Fix apache#1529 - In case the maven plugin fails to a unknown parameter, list all available endpoint parameters (cherry picked from commit 035cd06)
claudio4j
added a commit
to claudio4j/camel-kamelets
that referenced
this issue
Jul 7, 2023
- Fix apache#1529 - In case the maven plugin fails to a unknown parameter, list all available endpoint parameters (cherry picked from commit 035cd06)
claudio4j
added a commit
to claudio4j/camel-kamelets
that referenced
this issue
Jul 7, 2023
- Fix apache#1529 - In case the maven plugin fails to a unknown parameter, list all available endpoint parameters (cherry picked from commit 035cd06)
claudio4j
added a commit
to claudio4j/camel-kamelets
that referenced
this issue
Jul 7, 2023
- Fix apache#1529 - In case the maven plugin fails to a unknown parameter, list all available endpoint parameters (cherry picked from commit 035cd06)
claudio4j
added a commit
that referenced
this issue
Jul 7, 2023
- Fix #1529 - In case the maven plugin fails to a unknown parameter, list all available endpoint parameters
claudio4j
added a commit
that referenced
this issue
Jul 10, 2023
claudio4j
added a commit
that referenced
this issue
Jul 10, 2023
claudio4j
added a commit
that referenced
this issue
Jul 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the jira kamelet only supports basic authentication with username/password (oauth only for jira source), however the camel jira component accepts personal tokens as an additional secure way to authenticate, this way the user should not expose username or passwords.
This issue is to also adds support to personal token, which should be set in the access-token parameter.
The text was updated successfully, but these errors were encountered: