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
I'm trying to solve a proxy authorization problem. I have an agent built on ubi8 which does not have the gssntlmssp package. I can build it from source or download it from another host, but it has a number of dependencies, which makes the whole task difficult. The agent itself cannot connect to the proxy using the user and password and throws the error: GSSAPI operation failed with error - Unspecified GSS failure, my question is, is there any other way to authenticate on the proxy using the agent? Unfortunately, our only option is NTLM.
Versions
Ubi8, agent v3.240.1
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)
Operation system
Ubi8
Version controll system
No response
Azure DevOps Server Version (if applicable)
No response
The text was updated successfully, but these errors were encountered:
Describe your question
Hi,
I'm trying to solve a proxy authorization problem. I have an agent built on ubi8 which does not have the gssntlmssp package. I can build it from source or download it from another host, but it has a number of dependencies, which makes the whole task difficult. The agent itself cannot connect to the proxy using the user and password and throws the error: GSSAPI operation failed with error - Unspecified GSS failure, my question is, is there any other way to authenticate on the proxy using the agent? Unfortunately, our only option is NTLM.
Versions
Ubi8, agent v3.240.1
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Operation system
Ubi8
Version controll system
No response
Azure DevOps Server Version (if applicable)
No response
The text was updated successfully, but these errors were encountered: