Export to GitHub

typica - issue #99

NTLM authentication


Posted on Jul 23, 2010 by Swift Wombat

What steps will reproduce the problem? 1. Unix System HP UX 11.23 at datacenter 2. Internet access only thru a PROXY 3. DNS Server is able to resolve only Internal IP-addresses. It Will not be allowed to forward to a public Internet DNS server, due to Security Policy,Hence DNS server is unable to resolve ec2.amazonaws.com, s3.amazonaws.com 4. So Tried to add the IP address of the above in /etc/hosts file + We used Jec2.setProxyValues() to setProxy.

What is the expected output? What do you see instead?

we get the following error

Jul 23, 2010 11:51:36 AM com.xerox.amazonws.common.AWSQueryConnection configureHttpClient INFO: Proxy Host set to emea.nics.nxp.com:8080 Jul 23, 2010 11:51:37 AM org.apache.http.impl.client.AbstractAuthenticationHandler selectScheme WARNING: Authentication scheme ntlm not supported [Fatal Error] :7:3: The element type "BR" must be terminated by the matching end-tag "</BR>". Problem parsing returned message. com.xerox.amazonws.ec2.EC2Exception: Problem parsing returned message. at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2293) at com.xerox.amazonws.ec2.Jec2.describeRegions(Jec2.java:1881)

What version of the product are you using? On what operating system? TYPICA 1.7.0 , HP UX 11.23 on Itanium.

Please provide any additional information below. In the attached code's call to setProxyValues proxyname , port number is left empty .

Attachments

Comment #1

Posted on Jul 23, 2010 by Swift Wombat

With the new 1.7.2 Typica, i got the below error , but we donot have any password for the proxy that we use....

INFO: response = Access Denied

Access Denied (authentication_failed)

Your credentials could not be authenticated: "Credentials required.". You will not be permitted access until your credentials can be verified. This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
For assistance, contact your network support team.

Comment #2

Posted on Jul 26, 2010 by Swift Wombat

Issue resolved ... Thanks ... Please..

Comment #3

Posted on Jul 29, 2010 by Massive Kangaroo

(No comment was entered for this change.)

Status: WontFix