NTLM authentication

 Hi Rahul.

Let me clarify what I understand. You need NTLM authentication only to access the company intranet. Your Presto instance, otherwise works fine? If Presto itself needs credentials to work properly you need to set it up in adminserver under Server configuration. But I am assuming this is not the case.

If you want to access a resource which requires authentication, one way could be to register your service or page (as rest service) in Service Explorer, where you can specify the authentication details by checking the Require Authentication checkbox.

Do let me know if it helps while I think any other way of achieving this.

Hi,

Thanks for the reply. I'll try to elaborate on what I am trying to achieve.

I am trying to present the power of mashup's by getting some employee information from my company's intranet (which is just an '.asp' page and not exposed through any API) and then display it using tables/graphs/maps etc.

What happens when I actually accesss the intranet through a browser is, it asks for my credentials(NTLM authentication), which I provide and if it is correct then I get access. After this I navigate thorough a series of pages to reach the page which has the data that I need.

So what I tried in presto was, I used a direct invoke to access my intranet but it keeps showing that 'you are not authorized to view this page'. So how do I provide it with my credentials so that I can access the page, and also how do I navigate through the pages to get the information that I want?

Hope I was clearer this time...

Thanks,

Rahul

Hi Rahul,

Unfortunately directinvoke does not support NTLM authentication at this point in time.

Rahul,

Can you explore the possibility of publishing this page that you are accessing in Service Explorer as a REST service. And there in the publishing dialog you can also provide the NTLM authentication details by checking the Require Authentication checkbox. Since you were mentioning about using DirectInvoke, I am assuming you have a direct URL to your resource. You can use that URL while publising the service.

Do let me know it helps get your work done.

 Hi,

Thanks for the idea.. 

It seemed like it would work at first since the service gets created in a breeze, but it still gives me unauthorized access in the end.

Thanks,

Rahul

 In case you are still pursuing it, you could try with different authentication types and see if one of them goes through.

 there can be two things here

1) you r sitting behind a proxy , and you r trying the NTLM credentials .if this is the case ,you need to create the whitelist so that the presto server know that for that perticular domain , it shouldnt use proxy.(or you can just remove the proxy settings and try using the NTLM at the service creation time ).

2) You are using NTLM V2 , Jack be dsnt not support NTLM V2 as of now .

are there any patchs or anything avaliable  ?

Thanks