How do you set WAS traditional to allow basic authentication?

I’ve created a standalone EAR deployed on WebSphere that simply makes a SOAP call to TRIRIGA’s Connector for Business Applications (CBA). From the log file, it seems as though the basic authentication header is being ignored by TRIRIGA.

When deployed on WebSphere Liberty with the same version of TRIRIGA, I do not have this unauthorized problem, so it seems to be a security configuration disparity between WebSphere traditional and WebSphere Liberty (tested on and

From the SecurityLogger, the platform is correctly identifying the user. However, the status is Failed. Can anyone shed some ideas as to why there is a difference in security settings between Liberty and traditional? And how can I configure WebSphere traditional to allow basic authentication?

Continue reading


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s