[tverstraten]

When I launch the web 2.0 browser I get different behavoiur between browsing our application deployed on a server vs browsing it running locally. What I am trying to access is the first secured page in our site, when I try it locally the browser does not respond.

Specifically, the 2 cases are:
1) I start eclipse, launch the web 2.0 browser, type in http://ourtestwww/main . Since this is secured it loads the login jsp and presents it to me.

2) I start eclipse, use the myeclipse servers tab to start the app server locally. after its running I launch the web 2.0 browser and type in http://localhost/main . I get no response.

the deployments in both cases were identical. (i had just deployed from my local machine to the specified server).

I am running myeclipse 5.5.1GA (20070521)
eclipse 3.2.2.r322_v20070119
jdk 1.5.0_7-b03
jboss 4.0.5.GA (200610162339) with embedded tomcat
winxp pro

thanks

[Riyad Kalla]

Unfortunately I don’t have any way to trouble shoot this… not sure how you have the app servers setup that they would be different to present different situations to you.

MyEclipse’s part of the puzzle is deploying the project, if you are deploying the same project to two servers and one works and one doesn’t, that’s really a server-setup issue and not a MyEclipse issue unfortunately.

[tverstraten]

Riyad,

I think you missed my point. Its not the app servers that don’t work, its the web 2.0 browser. If I use IE, Firefox, etc both sites work fine throughout. If I use the web 2.0 browser the remote site works ok and for static html the local site works fine. The only case that doesn’t work is when I use the web 2.0 browser to login on the local site.

[Riyad Kalla]

Is the login an application login, or something like an apahce login with a .htaccess file? If it’s an application login (meaning you coded the login as part of the web app) that’s not a browser issue… but if you are using HTTPS or some other form of client-side authentication then that could definately be a Web2.0 browser issue.

[tverstraten]

Currently the login is https and we use form based with a custom loginmodule. so in our web.xml we have something like

<security-constraint>
<web-resource-collection>
<web-resource-name>portal</web-resource-name>
<url-pattern>/main</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>role1</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<realm-name>portal</realm-name>
<form-login-config>
<form-login-page>/login.jsp</form-login-page>
<form-error-page>/error.jsp</form-error-page>
</form-login-config>
</login-config>

then in our login-config.xml file we have a login module specified that is inside of our code that inherits from org.jboss.security.auth.spi.AbstractServerLoginModule.

if this is not supported by the web 2.0 browser, what are the recommended work arounds. i really don’t want to have to enable/disable our login process just to debug js.

[Riyad Kalla]

If you open up IE or Firefox locally and try and connect to your local running app… does the login work inside either of those browsers?

[Author]

Posts