You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment type (Please select at least one enviroment where you face this issue)
Self-Hosted
Microsoft Hosted
VMSS Pool
Container
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
N/A
Question
The documentation is unclear how InvokeRESTAPI authenticates to the server it's sending a request to. Generic service credentials have separate username and password fields, but neither the credential nor InvokeRESTAPI specify whether they will always be used with HTTP Basic authentication, or if there's any way to use the Bearer scheme, or something else.
jennings
changed the title
[Question]: What authentication methods are supported?
[Question]: What authentication methods are supported for InvokeRESTAPI?
Dec 10, 2024
Task name
InvokeRESTAPI
Task version
1
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
N/A
Question
The documentation is unclear how InvokeRESTAPI authenticates to the server it's sending a request to. Generic service credentials have separate username and password fields, but neither the credential nor InvokeRESTAPI specify whether they will always be used with HTTP Basic authentication, or if there's any way to use the Bearer scheme, or something else.
I looked up the InvokeRESTAPI task but found there's no actual code here, just a
HttpRequest
block since it's a server side task. Then I found the server side task authoring documentation, but it says only:The documentation should specify exactly how authentication is handled, even if the answer is, "Only HTTP Basic authentication is supported".
The text was updated successfully, but these errors were encountered: