How can I set the NTLM credential (as in my .NET controller) into a CURL request?

0

I am working on a .NET project. Into a controller of this project I am calling an external API specifying an authentication, in this way:

private NetworkCredential myCreds = new NetworkCredential("MYUSERNAME", "MYPASSWORD", "MYDOMAIN");



private CredentialCache = new CredentialCache();



string jsonRequest = urlBaseProtocolloApi + "/api/MY_ENDPOINT";



credCache.Add(new Uri(jsonRequest), "NTLM", myCreds);



HttpWebRequest spRequest = (HttpWebRequest)HttpWebRequest.Create(jsonRequest);

spRequest.Credentials = credCache;

spRequest.UserAgent = "Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0";

spRequest.Method = "GET";

spRequest.Accept = "application/json;odata=verbose";



ServicePointManager.ServerCertificateValidationCallback = delegate { return true; };



HttpWebResponse endpointResponse = (HttpWebResponse)spRequest.GetResponse();

It works perfectly fine.

As you can see I am using this NTLM protocol to perform the authentication into the called API.

My problem is that, for test reason, I want to perform this call using curl instead passing from my .NET controller.

I tried in this way:

curl -X POST -k -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

but obviously, since I'm not passing the credentials, I am obtaining this error message:

{"Message":"Authorization has been denied for this request."}

How can I try to set this NTLM on my curl request?

.net curl credentials ntlm

share|improve this question

asked Nov 21 '18 at 14:47

AndreaNobiliAndreaNobili

13.2k57181328

add a comment | 

0

I am working on a .NET project. Into a controller of this project I am calling an external API specifying an authentication, in this way:

private NetworkCredential myCreds = new NetworkCredential("MYUSERNAME", "MYPASSWORD", "MYDOMAIN");



private CredentialCache = new CredentialCache();



string jsonRequest = urlBaseProtocolloApi + "/api/MY_ENDPOINT";



credCache.Add(new Uri(jsonRequest), "NTLM", myCreds);



HttpWebRequest spRequest = (HttpWebRequest)HttpWebRequest.Create(jsonRequest);

spRequest.Credentials = credCache;

spRequest.UserAgent = "Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0";

spRequest.Method = "GET";

spRequest.Accept = "application/json;odata=verbose";



ServicePointManager.ServerCertificateValidationCallback = delegate { return true; };



HttpWebResponse endpointResponse = (HttpWebResponse)spRequest.GetResponse();

It works perfectly fine.

As you can see I am using this NTLM protocol to perform the authentication into the called API.

My problem is that, for test reason, I want to perform this call using curl instead passing from my .NET controller.

I tried in this way:

curl -X POST -k -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

but obviously, since I'm not passing the credentials, I am obtaining this error message:

{"Message":"Authorization has been denied for this request."}

How can I try to set this NTLM on my curl request?

.net curl credentials ntlm

share|improve this question

asked Nov 21 '18 at 14:47

AndreaNobiliAndreaNobili

13.2k57181328

add a comment | 

0

0

0

I am working on a .NET project. Into a controller of this project I am calling an external API specifying an authentication, in this way:

private NetworkCredential myCreds = new NetworkCredential("MYUSERNAME", "MYPASSWORD", "MYDOMAIN");



private CredentialCache = new CredentialCache();



string jsonRequest = urlBaseProtocolloApi + "/api/MY_ENDPOINT";



credCache.Add(new Uri(jsonRequest), "NTLM", myCreds);



HttpWebRequest spRequest = (HttpWebRequest)HttpWebRequest.Create(jsonRequest);

spRequest.Credentials = credCache;

spRequest.UserAgent = "Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0";

spRequest.Method = "GET";

spRequest.Accept = "application/json;odata=verbose";



ServicePointManager.ServerCertificateValidationCallback = delegate { return true; };



HttpWebResponse endpointResponse = (HttpWebResponse)spRequest.GetResponse();

It works perfectly fine.

As you can see I am using this NTLM protocol to perform the authentication into the called API.

My problem is that, for test reason, I want to perform this call using curl instead passing from my .NET controller.

I tried in this way:

curl -X POST -k -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

but obviously, since I'm not passing the credentials, I am obtaining this error message:

{"Message":"Authorization has been denied for this request."}

How can I try to set this NTLM on my curl request?

.net curl credentials ntlm

share|improve this question

asked Nov 21 '18 at 14:47

AndreaNobiliAndreaNobili

13.2k57181328

I am working on a .NET project. Into a controller of this project I am calling an external API specifying an authentication, in this way:

private NetworkCredential myCreds = new NetworkCredential("MYUSERNAME", "MYPASSWORD", "MYDOMAIN");



private CredentialCache = new CredentialCache();



string jsonRequest = urlBaseProtocolloApi + "/api/MY_ENDPOINT";



credCache.Add(new Uri(jsonRequest), "NTLM", myCreds);



HttpWebRequest spRequest = (HttpWebRequest)HttpWebRequest.Create(jsonRequest);

spRequest.Credentials = credCache;

spRequest.UserAgent = "Mozilla/4.0+(compatible;+MSIE+5.01;+Windows+NT+5.0";

spRequest.Method = "GET";

spRequest.Accept = "application/json;odata=verbose";



ServicePointManager.ServerCertificateValidationCallback = delegate { return true; };



HttpWebResponse endpointResponse = (HttpWebResponse)spRequest.GetResponse();

It works perfectly fine.

As you can see I am using this NTLM protocol to perform the authentication into the called API.

My problem is that, for test reason, I want to perform this call using curl instead passing from my .NET controller.

I tried in this way:

curl -X POST -k -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

but obviously, since I'm not passing the credentials, I am obtaining this error message:

{"Message":"Authorization has been denied for this request."}

How can I try to set this NTLM on my curl request?

.net curl credentials ntlm

.net curl credentials ntlm

share|improve this question

asked Nov 21 '18 at 14:47

AndreaNobiliAndreaNobili

13.2k57181328

share|improve this question

asked Nov 21 '18 at 14:47

AndreaNobiliAndreaNobili

13.2k57181328

share|improve this question

share|improve this question

asked Nov 21 '18 at 14:47

AndreaNobiliAndreaNobili

13.2k57181328

asked Nov 21 '18 at 14:47

AndreaNobiliAndreaNobili

13.2k57181328

asked Nov 21 '18 at 14:47

AndreaNobiliAndreaNobili

13.2k57181328

13.2k57181328

add a comment | 

add a comment | 

1 Answer
1

active

oldest

votes

0

Your .net is automatically using kerberos or ntlm (aka WIA). In curl you have to use the --ntlm or --negotiate or --anyauth and the --user flags.

Some examples:

This will try ntlm:
curl -X POST -k --ntlm --user domainuser:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try negotiate:
curl -X POST -k --negotiate --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try kerberos or ntlm depending on the IIS setup:
curl -X POST -k --anyauth --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

Known bugs:
There two known bugs in curl related to ntlm HTTPS and POST requests:

1. Curl drops the payload for POST requests with ntlm:
   https://github.com/curl/curl/issues/2431
   


2. NTLM return 401 when "Extended protection" is Required by IIS: https://github.com/curl/curl/issues/3280. To fix the issue turn off extended protection if you can and live with the security traits (https://docs.microsoft.com/en-us/iis/configuration/system.webserver/security/authentication/windowsauthentication/extendedprotection/#how-to).

share|improve this answer

answered Nov 29 '18 at 10:02

George OikonomouGeorge Oikonomou

2,27312135

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53414599%2fhow-can-i-set-the-ntlm-credential-as-in-my-net-controller-into-a-curl-request%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

active

oldest

votes

active

oldest

votes

0

Your .net is automatically using kerberos or ntlm (aka WIA). In curl you have to use the --ntlm or --negotiate or --anyauth and the --user flags.

Some examples:

This will try ntlm:
curl -X POST -k --ntlm --user domainuser:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try negotiate:
curl -X POST -k --negotiate --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try kerberos or ntlm depending on the IIS setup:
curl -X POST -k --anyauth --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

Known bugs:
There two known bugs in curl related to ntlm HTTPS and POST requests:

1. Curl drops the payload for POST requests with ntlm:
   https://github.com/curl/curl/issues/2431
   


2. NTLM return 401 when "Extended protection" is Required by IIS: https://github.com/curl/curl/issues/3280. To fix the issue turn off extended protection if you can and live with the security traits (https://docs.microsoft.com/en-us/iis/configuration/system.webserver/security/authentication/windowsauthentication/extendedprotection/#how-to).

share|improve this answer

answered Nov 29 '18 at 10:02

George OikonomouGeorge Oikonomou

2,27312135

add a comment | 

0

Your .net is automatically using kerberos or ntlm (aka WIA). In curl you have to use the --ntlm or --negotiate or --anyauth and the --user flags.

Some examples:

This will try ntlm:
curl -X POST -k --ntlm --user domainuser:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try negotiate:
curl -X POST -k --negotiate --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try kerberos or ntlm depending on the IIS setup:
curl -X POST -k --anyauth --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

Known bugs:
There two known bugs in curl related to ntlm HTTPS and POST requests:

1. Curl drops the payload for POST requests with ntlm:
   https://github.com/curl/curl/issues/2431
   


2. NTLM return 401 when "Extended protection" is Required by IIS: https://github.com/curl/curl/issues/3280. To fix the issue turn off extended protection if you can and live with the security traits (https://docs.microsoft.com/en-us/iis/configuration/system.webserver/security/authentication/windowsauthentication/extendedprotection/#how-to).

share|improve this answer

answered Nov 29 '18 at 10:02

George OikonomouGeorge Oikonomou

2,27312135

add a comment | 

0

0

0

Your .net is automatically using kerberos or ntlm (aka WIA). In curl you have to use the --ntlm or --negotiate or --anyauth and the --user flags.

Some examples:

This will try ntlm:
curl -X POST -k --ntlm --user domainuser:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try negotiate:
curl -X POST -k --negotiate --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try kerberos or ntlm depending on the IIS setup:
curl -X POST -k --anyauth --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

Known bugs:
There two known bugs in curl related to ntlm HTTPS and POST requests:

1. Curl drops the payload for POST requests with ntlm:
   https://github.com/curl/curl/issues/2431
   


2. NTLM return 401 when "Extended protection" is Required by IIS: https://github.com/curl/curl/issues/3280. To fix the issue turn off extended protection if you can and live with the security traits (https://docs.microsoft.com/en-us/iis/configuration/system.webserver/security/authentication/windowsauthentication/extendedprotection/#how-to).

share|improve this answer

answered Nov 29 '18 at 10:02

George OikonomouGeorge Oikonomou

2,27312135

Your .net is automatically using kerberos or ntlm (aka WIA). In curl you have to use the --ntlm or --negotiate or --anyauth and the --user flags.

Some examples:

This will try ntlm:
curl -X POST -k --ntlm --user domainuser:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try negotiate:
curl -X POST -k --negotiate --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

This will try kerberos or ntlm depending on the IIS setup:
curl -X POST -k --anyauth --user user:password -d @invio_a_protocollo.json https://my_machine:13003/API_CONTEXT/api/MY_ENDPOINT --header "Content-Type:application/json

Known bugs:
There two known bugs in curl related to ntlm HTTPS and POST requests:

1. Curl drops the payload for POST requests with ntlm:
   https://github.com/curl/curl/issues/2431
   


2. NTLM return 401 when "Extended protection" is Required by IIS: https://github.com/curl/curl/issues/3280. To fix the issue turn off extended protection if you can and live with the security traits (https://docs.microsoft.com/en-us/iis/configuration/system.webserver/security/authentication/windowsauthentication/extendedprotection/#how-to).

share|improve this answer

answered Nov 29 '18 at 10:02

George OikonomouGeorge Oikonomou

2,27312135

share|improve this answer

share|improve this answer

answered Nov 29 '18 at 10:02

George OikonomouGeorge Oikonomou

2,27312135

answered Nov 29 '18 at 10:02

George OikonomouGeorge Oikonomou

2,27312135

answered Nov 29 '18 at 10:02

George OikonomouGeorge Oikonomou

2,27312135

2,27312135

add a comment | 

add a comment | 

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question. Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.


• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53414599%2fhow-can-i-set-the-ntlm-credential-as-in-my-net-controller-into-a-curl-request%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Name

Name

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

Email

Required, but never shown

This page is only for reference, If you need detailed information, please check here