Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 900
  • Last Modified:

Make Tomcat (and Weblogic) ignore custom error codes

Hi Experts,

we have the following scenario: We are supposed to implement a Single Sign On between an application and a Portal. This Portal is deployed and running under Oracle Application Server. So the Oracle Internet Directory shall be used as central User Repository. Due to certain constraints we are forced to deploy and run our application on Weblogic in Production and Tomcat (5.0.31) in Development Environment. Now what i have reached so far is to make a single sign on possible by tunneling every request to logged in pages through an apache proxy url defined in the Oracle iAS and mod_osso checking this url.

Here is my question now: As the response flow of our application is interpreted by Weblogic(Tomcat) first on a tunneled response, also Error (Status) Codes will be interpreted here first. This means, that i cannot send a Custom Error (Status) Code that will be known by mod_osso in order to have a certain reaction like logout (code 470), or forced re-login etc.

Is it possible, to configure Tomcat, respectively an application so that a certain error code won't be interpreted????

Any help would be greatly appreciated!!!
thx in advance!

Alex Hepp
0
heppa
Asked:
heppa
  • 2
  • 2
1 Solution
 
KnightFireCommented:
Is your portal the front end?
Do you use tomcat on its own or JBoss? If you use JBoss in development then both WebLogic and JBoss will allow you to deploy custom authentication modules, you could develop a custom authentication token type, or use SAML.
Also as it sounds like you are writing an application that produces information for use in a portal, perhaps you should make the back end server a portal too and use WSRP between the front end and back end portals.
0
 
heppaAuthor Commented:
I think, i was not clear enough on this. We don't have the chance on deciding the environment. meaning, that we might not deploy our application in production environment under anything else than Weblogic. And the development environment will be a single tomcat instance. We are not allowed to use JBoss as Development Environment (don't ask me why). We have two frontends (one being the portal, the other one being our application). The relation between the portal and our application is simply, that certain information, that is being displayed by our application is being linked from the portal. But as it is depending on a user profile (ideally with authorization), the customer asked us to develop a Single Sign On having an Oracle Internet Directory running in the environment together with the portal.

But that all isn't the problem... That was just to clarify the situation / scenario. Thanks a lot for helping me anyway.

all I want to know, whether it is possible to make Weblogic / Tomcat ignore certain HTTP Status Codes or simply continue processing.

An Answer like "No, this isn't possible at all" with a prooven reason or example would also do! Than i will find out about alternatives ;)
0
 
KnightFireCommented:
It is not possible in weblogic (as far as I am aware),
You could probably make Tomcat do it by modifying the source and re-compiling,
0
 
heppaAuthor Commented:
Thanks KnightFire! But recompiling tomcat wouldn't be the plan, as i couldn't do that with weblogic ;)

I thought it might be possible providing a new connector or something. But if this doesn't work in Weblogic, i have to find a different way.

If anyone knows about a solution with this status / error codes, i will wait some days, and then accept KnightFire's answer.

Thanks a lot!
alex
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now