My Oracle Support Banner

Authorization Fails With "HTTP/1.1 401 Authorization Required" (Doc ID 1643570.1)

Last updated on OCTOBER 10, 2020

Applies to:

Oracle Payments - Version 12.2.3 to 12.2.4 [Release 12.2]
Information in this document applies to any platform.


On : 12.2.3 version, FC Core

When attempting to perform an authorization through tunneling to a web servlet which handles integration with Paymentech provider and is protected by simple HTTP password, a "HTTP/1.1 401 Authorization Required" error is seen in the debug log:

iby.engine.TransmitConfig.transmit(3arg-security) Enter
iby.engine.TransmitConfig.transmit(3arg-security) starting to tunnel

..... destination url=http://<server.domain>:<port>/paymentech/oramipp_ptk phase 2: checking proxy settings ENTER no proxy domain=<domain> phase 3: opening socket

..... phase 2: writing POST headers ENTER replacing protocol https with http EXIT OapfDelEnvLen: 1667 content len=Content-length: 1772 setting the auth header last=Authorization: Basic XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX== phase 3: writing POST body phase 4: reading HTTP response bytes read in response=577 closing socket phase 5: parsing HTTP response ENTER phase 1: converting raw bytes into a string using iso8859-1 seperator index=279 phase 2: parsing the HTTP headers "raw header content:
HTTP/1.1 401 Authorization Required
Date: Tue, 25 Feb 2014 08:31:33 GMT
Server: Oracle-Application-Server-11g
WWW-Authenticate: Basic realm=""iPayment servlet access""
Content-Length: 294
Connection: close
Content-Type: text/html; charset=iso-8859-1
X-Pad: avoid browser bug" "header not well-formatted: HTTP/1.1 401 Authorization Required


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.