[Bug][JIRA Service API TOKEN] Jira API Gateway: saved service-account token truncated by varchar(255), causing Base64 errors and HTTP 500
维护者通常 2 天内回复
评估
调研方向
Start by tracing how Jira connection tokens are saved and loaded, then inspect the database schema or model for the token column and the code that decodes it. Reproduce by saving a scoped Atlassian service-account token and reopening the connection; the report says widening the column to LONGTEXT and recreating the connection resolves it. Done when the saved token is preserved and the Jira connection can be reopened without a Base64 error.
由索引模型根据 Issue 内容生成。
描述
Search before asking
- I had searched in the issues and found no similar issues.
What happened
Jira Cloud connections using Atlassian API Gateway and a scoped service-account API token pass Test Connection, but fail after saving.
The issue reproduced in both development and production. Widening the database’s token column to LONGTEXT and recreating the affected connection resolved it.
Version / environment
DevLake backend: v1.0.3-beta17
Config UI: v1.0.3-beta17
Deployment: AWS ECS Fargate
Database: MySQL-compatible, InnoDB, utf8mb4
Connector: Jira Cloud (Atlassian API Gateway)
Authentication: scoped Atlassian service-account API token (AccessToken)
What do you expect to happen
illegal base64 data at input byte 252
Wraps: (2) illegal base64 data at input byte 252
Error types: (1) *hintdetail.withDetail (2) base64.CorruptInputError
How to reproduce
Steps to reproduce
Create a Jira connection.
Select Jira Cloud (Atlassian API Gateway).
Enter a valid site Cloud ID and scoped service-account token.
Click Test Connection—it succeeds.
Save the connection.
Open Add Data Scopes or reload Jira connections.
Anything else
No response
Version
DevLake backend: v1.0.3-beta17
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
- 主要语言
- Go
- 星标
- 3.2k
- 派生
- 832
- 平均合并
- 1 天 21 小时
- 30 天内合并 PR
- 78
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/devlake 的其他 Issue
-
[Bug][Testmo] Runs, milestones and automation runs: only the first 100 are collected可能已有人在做 @ShivamSharma43 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
[Bug][Tempo] Worklog domain ids lack the connection id, so connections with the same worklog id overwrite each other可能已有人在做 @ShivamSharma43 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
[Bug][linker] LinkPrToIssue never matches lowercase issue keys (e.g. in branch names)可能已有人在做 @VictorColomb 于 4 天前认领。 未关闭type/bug
难度 2/5 1-3 小时 新手友好度 78/100
apache/devlake#9283 · 1 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 60/100
维护者通常 2 天内回复
-
type/bug
难度 4/5 3-5 天 新手友好度 51/100
维护者通常 2 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
SAP/crossplane-provider-btp#1175 ·
维护者通常 1 天内回复
-
adk: stream concatenation errors bypass retry and failover可能已有人在做 @OUAO-FRANK 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
google/osv-scalibr#2586 ·
维护者通常 2 天内回复
-
needs-triage
难度 2/5 1-3 小时 新手友好度 72/100
stacklok/toolhive-catalog#1890 ·
维护者通常 1 天内回复
-
heap: pushing an item that is already queued corrupts the index可能已有人在做 @lbarrosby 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
kubernetes-sigs/kwok#1800 ·
维护者通常 1 天内回复