-
Notifications
You must be signed in to change notification settings - Fork 20
CXF : unable to login on soap service #11
Comments
Let me run a test, and I'll get back to you |
I made some update to the WSDL file and the sapi.jar file. Can you please resync the repo and retry? |
Many thanks for your quick reply ! Same thing with fresh new deployment. In cxf-test you are using a boolean to switch between CSP or PSC login ; is there something I need to specify to login using PSC and SOAP ? I haven't found any detection mechanism in code that instantiate pscConnectOptions or cspConnectOptions. Have you a working authentication example request/scenario using SOAP requests ? |
I never tried to use soap directly. |
Ok. Is it possible to expose directly "loginPsc + loginCsp" additionally to "login" soap actions ? (each one linked to corresponding type "pscConnectOptions + cspConnectOptions") Or adding another parameter in "login" to specify "auth_type(psc|csp)" in order to create the object with the right class ? ("pscConnectOptions"/"cspConnectOptions" and not "connectOptions" => like you do in your cxf-test app with a boolean) I suppose it's this test that fails (or equivalent method in safekeeping-external/etc) : https://github.com/vmware/safekeeping/blob/74f91eb216d8003683f251dab109fa0b0eb6e148/safekeeping-cxf/src/main/java/com/vmware/safekeeping/cxf/SapiImpl.java#L749-L761 Object never match conditions instanceOf(pscConnectOptions|cspConnectOptions) because it's always created with parent ConnectOptions class through soap service (instead of child classes pscConnectOptions/cspConnectOptions) |
Yes I can. Let me work on that |
I created 2 new API loginCsp and LoginPsc |
It works !! :) (I've made some corrections in prepare.sh to make it work) I get a token in xml response, I've tried to pass it to HTTP Auth-token header but it throws a 500 with UnrecognizedToken exception. Am I using it the right way ? |
do you get this error with the connect method? |
I was getting this error with isConnected (loginPsc, then isConnected [with Auth-token]). I've made new tests, so now :
I confirm that using workflow loginPsc/connect/isConnected (instead of loginPsc/isConnected) fixes I'm not using any language, only pure SOAP requests ; I'm querying /sdk entrypoint with SoapUI - wich generates stubs from SOAP wsdl/xsd url (great for basic/quick testing : in soapUI, create new SOAP project and paste EDIT : I'm using |
Describe the bug
Hi,
I'm trying to connect using soap service provided by safekeeping-cxf and experiencing issues.
The getVersion() soap operation is working fine.
When I login() with authServer/base64/user/password/port I get an
Unsupported authentication type:class com.vmwar e.safekeeping.external.type.options.ConnectOptions
.It seems that "options" element (of login() operation) is linked to "ConnectOptions" causing the object to never beeing recognized as
instanceOf pscConnectOptions
... and so failing with previous error.Is it a bug or am i missing something ? :)
Reproduction steps
The text was updated successfully, but these errors were encountered: