jira: update jira JWT subject per Atlassian's recent GDPR changes #389
Conversation
|
This PR (HEAD: 344bb60) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/oauth2/+/185081 to see it. Tip: You can toggle comments from me using the |
|
any update here? we have this hacked out in our vendor libs currently as it's needed to fix a production integration. |
|
Fixes #312 |
bradfitz
changed the title
|
Message from Brad Fitzpatrick: Patch Set 3: Run-TryBot+1 Code-Review+2 Please don’t reply on this GitHub thread. Visit golang.org/cl/185081. |
|
Message from Gobot Gobot: Patch Set 3: TryBots beginning. Status page: https://farmer.golang.org/try?commit=2c54c384 Please don’t reply on this GitHub thread. Visit golang.org/cl/185081. |
Recently, Atlassian decided to remove `userKey` from JWT construction b/c they determined that it could contain personally identifiable information. They've since switched to the user account ID. This change updates the jira JWT to reflect these recent change. Fixes #312 Change-Id: I4bd66cf925fdf38e02dd665befb5ab5f19f14ee7 GitHub-Last-Rev: 344bb60 GitHub-Pull-Request: #389 Reviewed-on: https://go-review.googlesource.com/c/oauth2/+/185081 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
|
This PR is being closed because golang.org/cl/185081 has been merged. |
4 participants
Recently, Atlassian decided to remove
userKeyfrom JWT construction b/c they determined that it could contain personally identifiable information. They've since switched to the user account ID. This change updates the jira JWT to reflect these recent change.Fixes #312