"appContext" is not returned correctly at service side during unified jsr 196 pipe invokation for web services security.

[glassfishrobot]

The problem is during unified jsr 196 pipe invokation for web services security, when the server auth config or server auth context gets the "appContext" and policy map, we need to get actual deployed WSP end point from either of these two, but

appContext comes as "

{http://localhost:8080/openfm/ SecurityTokenService/}

ISecurityTokenService_Port", not sure how to get service endpoint from this directly.

So tried :

1)WSDLPort port =(WSDLPort)map.get("WSDL_MODEL"); String endpoint = port.getAddress().getURL().toString(); This still gives endpoint as static WSDL defined service / STS end point.

2)WSEndpoint endPoint = (WSEndpoint)map.get("ENDPOINT"); WSDLPort port = endPoint.getPort(); String endpoint = port.getAddress().getURL().toString(); This still gives endpoint as static WSDL defined service / STS end point.

Hence we are not able to get the actual deployed WSP end point. This is the problem.

Environment

Operating System: All Platform: All

Affected Versions

[current]

[glassfishrobot]

Reported by mrudul_uchil@java.net

[glassfishrobot]

kumarjayanti@java.net said: Would it help if we introduce a small SPI call here and allow FAM to define what the appContextID needs to be. ?

Because from a JAXWS perspective here is the final work from JAXWS experts :

As I said we cannot give the address during intialization. There is no way to get this from servlet api(as the request could be coming through load balancers, different networking equipments etc), and hence the servlet api doesn't provide this info. One option is to add a metro-specific property to web.xml to give this information, but one needs to be aware of networking deployments. GlassFish impl gets this info from some glassfish admin configuration, similarly it could be different for other containers.

We can only give the address during service invocation(usually using HttpServletRequest to get the address).

[glassfishrobot]

mrudul_uchil@java.net said: Kumar and Jitu have email exchanges to get to a solution but looks like there is no proper solution available. FAM will move ahead with its own workaround of determining WSP profile based on static service end point.

[glassfishrobot]

kumarjayanti@java.net said: While the latest solution does not work, it appears FAM team has gone ahead with a workaround. Marking the Bug for a later release.

[glassfishrobot]

kumarjayanti@java.net said: FAM is currently using a WorkAround. While we would like to close the Bug FAM is still of the opinion that metro should do something about it. So marking target milestone to 2.0.

[glassfishrobot]

kumarjayanti@java.net said: There is really not much that we can do beyond this for 2.0. Will investigate for 2.1.

[glassfishrobot]

@vbkumarjayanti said: This was an opensso requirement but is no longer relevant given the deprecated status of opensso

[glassfishrobot]

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

[glassfishrobot]

Marked as won't fix on Saturday, December 11th 2010, 8:47:27 pm