Smalltalk › Pharo › Pharo Smalltalk Developers

Proxy with NTLM authentication?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

4 messages Options

Bernhard Pieber-3

Proxy with NTLM authentication?

Hi all,

I would like to use Pharo behind a corporate firewall with a proxy with NTLM authentication. Having read the thread "Proxy with authentication support" (http://lists.gforge.inria.fr/pipermail/pharo-project/2009-May/008717.html) I thought I might try if it works with NTLM. Short version: It doesn't. ;-)

Has someone solved that particular problem?

Thanks for your support!

Cheers,

Bernhard

Long version:

If I do:

HTTPSocket httpGet: 'http://www.pieber.com'

I get:

'HTTP/1.1 400 Bad Request
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Proxy-Connection: close
Connection: close
Content-Length: 1251<HTML><HEAD>
<TITLE>Invalid username/password</TITLE>
</HEAD>
<BODY>

<big></big> 

<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>

<big>Invalid username/password (bad_credentials)</big>
 
 

</TD></TR>
<TR><TD>

 Your username or password were sent using an invalid/unrecognized format.
 Please close your browser window.
 Then, either contact technical support,
 or try again using a different username/password combination.
 
 There are two possible causes:
 <ul>
 <li>Your username or password contains non-ASCII characters,
 and the ProxySG is not configured to use the same authentication character
 encoding as is being used by your web browser.
 <li>Your username or password is too long.
 (The limits for the username and password are 64 bytes each,
 after being translated to UTF-8.)
 </ul>
 


</TD></TR>
<TR><TD>

</TD></TR>
<TR><TD>

 
For assistance, contact your network support team.

</TD></TR>
</TABLE>
</blockquote>

</BODY></HTML>
'

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan van de Sandt

Re: Proxy with NTLM authentication?

Hello,

I don't think the HTTPSocket class supports proxies with NTLM authentication. There is an alternative: the CurlPlugin, this plugin wraps the libcrul C library and this library supports NTML authentication, see: http://wiki.squeak.org/squeak/5865

Jan.

2009/5/25 Bernhard Pieber <[hidden email]>

Hi all,

I would like to use Pharo behind a corporate firewall with a proxy with NTLM authentication. Having read the thread "Proxy with authentication support" (http://lists.gforge.inria.fr/pipermail/pharo-project/2009-May/008717.html) I thought I might try if it works with NTLM. Short version: It doesn't. ;-)

Has someone solved that particular problem?

Thanks for your support!

Cheers,
Bernhard

Long version:
If I do:

HTTPSocket httpGet: 'http://www.pieber.com'

I get:
'HTTP/1.1 400 Bad Request
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Proxy-Connection: close
Connection: close
Content-Length: 1251<HTML><HEAD>
<TITLE>Invalid username/password</TITLE>
</HEAD>
<BODY>

<big></big> 

<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>

<big>Invalid username/password (bad_credentials)</big>
 
 

</TD></TR>
<TR><TD>

 Your username or password were sent using an invalid/unrecognized format.
 Please close your browser window.
 Then, either contact technical support,
 or try again using a different username/password combination.
 
 There are two possible causes:
 <ul>
 <li>Your username or password contains non-ASCII characters,
 and the ProxySG is not configured to use the same authentication character
 encoding as is being used by your web browser.
 <li>Your username or password is too long.
 (The limits for the username and password are 64 bytes each,
 after being translated to UTF-8.)
 </ul>
 


</TD></TR>
<TR><TD>



</TD></TR>
<TR><TD>

 
For assistance, contact your network support team.

</TD></TR>
</TABLE>
</blockquote>

</BODY></HTML>
'

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Hockenberry

Re: Proxy with NTLM authentication?

In reply to this post by Bernhard Pieber-3

CONTENTS DELETED

The author has deleted this message.

Steve Wirts

Re: Proxy with NTLM authentication?

I have wrestled with this problem from within java years ago, before a solution existed, the solution that finally evolved was an API in java to talk LDAP, specifically to microsoft active directory servers. Validation and NT user/group information them becomes available regardless of what platform the client is running on.

just an thought towards a very general solution.

2009/5/25 Marco Schmidt <[hidden email]>

I'm using Pharo "sometimes" behind a coorperate firewall. The following snippet helps me to setup squeak/pharo for me:

HTTPSocket useProxyServerNamed: 'proxyhsotname' port: 80 proxyUser: 'DOMAIN\USERNAME' password: 'HelloWorld42'.

Another alternative is to use an tool like PROXIMOTRON. This tools creates a local proxy server which forwards http connections to your corporate firewall. WARNING: This could be against your coorporates policy.

Marco Schmidt

2009/5/25 Bernhard Pieber <[hidden email]>

Hi all,

I would like to use Pharo behind a corporate firewall with a proxy with NTLM authentication. Having read the thread "Proxy with authentication support" (http://lists.gforge.inria.fr/pipermail/pharo-project/2009-May/008717.html) I thought I might try if it works with NTLM. Short version: It doesn't. ;-)

Has someone solved that particular problem?

Thanks for your support!

Cheers,
Bernhard

Long version:
If I do:

HTTPSocket httpGet: 'http://www.pieber.com'

I get:
'HTTP/1.1 400 Bad Request
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Proxy-Connection: close
Connection: close
Content-Length: 1251<HTML><HEAD>
<TITLE>Invalid username/password</TITLE>
</HEAD>
<BODY>

<big></big> 

<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>

<big>Invalid username/password (bad_credentials)</big>
 
 

</TD></TR>
<TR><TD>

 Your username or password were sent using an invalid/unrecognized format.
 Please close your browser window.
 Then, either contact technical support,
 or try again using a different username/password combination.
 
 There are two possible causes:
 <ul>
 <li>Your username or password contains non-ASCII characters,
 and the ProxySG is not configured to use the same authentication character
 encoding as is being used by your web browser.
 <li>Your username or password is too long.
 (The limits for the username and password are 64 bytes each,
 after being translated to UTF-8.)
 </ul>
 


</TD></TR>
<TR><TD>



</TD></TR>
<TR><TD>

 
For assistance, contact your network support team.

</TD></TR>
</TABLE>
</blockquote>

</BODY></HTML>
'

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project