Daniel-alisi opened a new issue, #9328: URL: https://github.com/apache/devlake/issues/9328
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) 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? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
