To log in to our corporate Jira, we use 2FA with Okta or Microsoft. I don't know when it was set up, so I tried with SESSION and with TOKEN.

For SESSION, I get this error: Error: error creating token 404: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><status><status-code>404</status-code><message>null for uri: https://jira.xxxx.xx//rest/auth/1/session</message></status>

And for TOKE it looks like this: Error: Project XXX doesn't exist on https://jira.xxxx.xx, or authentication credentials for (xxxx@xxxxx.xx) are invalid

Are such SSO setups supported, or only setups with email/password?

I don't think the Jira bridge does that: https://github.com/MichaelMure/git-bug/blob/master/bridge/jira/config.go

I'm not using Jira so it's unlikely I'll work on that, would you give it a try? That said, I suppose using a SSO means that the credential would expire quickly and would need to be renew periodically? That's not impossible but kind of an hassle. Maybe that would require a new command under bridge auth? renew ? sso ?

I tried the curl command

curl \
  --data '{"username":"<username>", "password":"<password>"}' \
  --header "Content-Type: application/json" \
  --request POST \
  <serverUrl>/rest/auth/1/session

from https://github.com/MichaelMure/git-bug/blob/master/doc/jira_bridge.md and got the following error: {"errorMessages":["Login failed"],"errors":{}} Hence my hopes are low.

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/rotten 11 months ago

github-actions (github-actions) removed label lifecycle/stale 11 months ago

sudoforge removed label lifecycle/dormant 7 months ago