-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't integrate azure devops with reportportal #64 #2055
Comments
@maciekpazola , I have a weird idea for you : could you please try to rename directly in Postgres database? |
I have tried it, now the request looks correct, but I got 400 error with message: { |
Why in payload of the integration call it's OAUTH instead of PAT? |
Build using following patch: reportportal/plugin-bts-azure#70, it might work for you as well. We are currently running it with ADO 2019 On-prem and ADO Cloud together. |
Good afternoon,
I attempted to integrate ReportPortal with our on-premise Azure DevOps, but encountered an issue. The request to trigger the integration contains forbidden characters—specifically, the request call is named "Azure%20DevOps." Our Azure DevOps configuration blocks such characters by default.
Is there any workaround available from ReportPortal, or is it possible to adjust the naming convention within ReportPortal to avoid this issue?
Request url: http://serverurl/api/v1/integration/Azure%20DevOps
Request status: 409 Conflict
Response:
{
"errorCode": 40302,
"message": "Unable to interact with the integration. Unable to connect to Azure DevOps. Code: 400, Message: A potentially dangerous Request.Path value was detected from the client (:)."
}
Under this link you can find ticket about the specific issue:
https://learn.microsoft.com/en-us/answers/questions/1509257/how-to-solve-error-a-potentially-dangerous-request
Best regards,
Maciej Pazoła
The text was updated successfully, but these errors were encountered: