kestra-io / kestra-io/plugin-sentry
Sentry.io plugin failing with deprecated userinfo component
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 5
Description
Describe the issue
The Sentry DSN has a userinfo component specified to authenticate to Sentry (i.e. https://PUBLIC:SECRET@UNIQUE_ID.sentry.io/PROJ). As a result which ever Java library you are using to handle HTTP requests is failing any task that uses the Sentry plugin.
2025-07-28 01:12:39.862 org.apache.hc.client5.http.ClientProtocolException: Request URI authority contains deprecated userinfo component
2025-07-28 01:12:39.862 Request URI authority contains deprecated userinfo component
I have been searching for alternative ways to specify the PUBLIC and SECRET (such as in the payload) but have been unable to find reference to a workaround. I suspect that it may be necessary to specify the PUBLIC and SECRET in the schema so that they can be sent as an authentication header instead of in the URL.
Environment
- Kestra Version: 0.22.8
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a Sentry plugin task with the DSN format shown and inspect the Java HTTP request handling that rejects the userinfo component. Determine how the PUBLIC and SECRET values are currently sent; done means the plugin can authenticate to Sentry without the deprecated userinfo error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100