Bug 2445 - Holder problem
: Holder problem
Status: NEW
: Java WS Security
Authentication
: development
: PC Linux
: P5 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2004-12-13 12:46 by
Modified: 2007-09-12 16:31 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2004-12-13 12:46:37
Running into a bit of trouble with the code in
AuthUtil.getOperationName(). The secure conversation stuff has a
operation that looks like this:

        <operation name="Challenge">
            <input 
                message="wst:RequestSecurityTokenResponseMsg"/>
            <output 
                message="wst:RequestSecurityTokenResponseMsg"/>
        </operation>

which results in the following signature:

public void challenge(RequestSecurityTokenResponseTypeHolder response)
        throws RemoteException

Now, getOperationName() tries to figure out the operation name by
walking the operations defined in the service desc and doing a parameter
QName comparison. The problem is that for the above method the QName for
the in parameter seems to be 

NS:http://service.secureconv.authentication.security.impl.wsrf.globus.org
Localpart:response

which of course does not match the top level element QName, so stuff
breaks. I suspect that this will be the case for any service that has
the same in and output messages on a operation. Any idea on how to fix
this?

/Sam
------- Comment #1 From 2004-12-13 12:47:39 -------
Just added this so it doesn't get lost. Not urgent.

/Sam
------- Comment #2 From 2007-09-12 16:31:18 -------
Reassigning to current wsrf developer to close/fix as appropriate.