Mex service communication regression with latest Metro build

[glassfishrobot]

Mex service communication regression with latest Metro build

MEX0008:Failed to parse metadata returned from server at http://localhost:8080/opensso/sts/mex using protocol SOAP_1_2. Continuing attempts. --[HTTP request]-- Host: localhost:8080 Content-length: 499 Content-type: text/xml; charset="utf-8" Accept: text/html, image/gif, image/jpeg, *; q=.2, /**; q=.2 Connection: keep-alive Soapaction: "http://schemas.xmlsoap.org/ws/2004/09/transfer/Get" User-agent: Java/1.5.0_13 <soap-env:Envelope xmlns:soap-env='http://schemas.xmlsoap.org/soap/envelope/' xmlns:wsa='http://www.w3.org/2005/08/addressing'>http://schemas.xmlsoap.org/ws/2004/09/transfer/Get</wsa:Action>http://localhost:8080/opensso/sts/mex</wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address></wsa:ReplyTo>uuid:778b135f-3fdf-44b2-b53e-ebaab7441e40</wsa:MessageID></soap-env:Header></soap-env:Envelope>

Unsupported Content-Type: text/xml; charset="utf-8" Supported ones are: [application/soap+xml] com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/xml; charset="utf-8" Supported ones are: [application/soap+xml] at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:292) at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:129) at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287) at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276) at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:93) at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:432) at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244) at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135) at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:129) at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:160) at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Environment

Operating System: All Platform: All

Affected Versions

[1.3]

[glassfishrobot]

Reported by mrudul_uchil@java.net

[glassfishrobot]

kumarjayanti@java.net said: After some investigation it appears to me that the earlier implementation was probably having a Bug and what we have now in the ServerSecurityTube is correct.

However the FAM AuthContext implementation should make sure it returns AuthStatus.SUCCESS for MEX requests, and that seems to be the only correct way to handle this.

Because the Metro ServerSecurityTube cannot call doInvoke as suggested by Malla when the AuthStatus returned is not AuthStatus.SUCCESS. It can only call doReturnWith in those cases. Because if the Auth Module indicates an Authentication Failure then we are not supposed to allow the request to reach the EndPoint.

It is a bit puzzling to me how things were working in earlier version. Because even there we were returning back instead of invoking the Mex Endpoint.

Please investigate my suggestion about returning AuthStatus.SUCCESS from your 196 modules for Mex requests. I am marking the bug as Invalid. If you think otherwise please feel free to re-open with Justification.

[glassfishrobot]

kumarjayanti@java.net said: reopening after further discussion with FAM team.

[glassfishrobot]

kumarjayanti@java.net said: checked in a Fix to Trunk and METRO-1_3-BRANCH

[glassfishrobot]

Was assigned to kumarjayanti@java.net

[glassfishrobot]

This issue was imported from java.net JIRA WSIT-972

[glassfishrobot]

Marked as fixed on Tuesday, July 22nd 2008, 10:44:57 am