|Accessing Stardust dynamic web services on Weblogic 10.3 results in 401 Unauthorized response [message #1008817]
||Wed, 13 February 2013 22:41
| Jan Hendrik Scheufen
Registered: October 2011
I've got a Stardust Spring Portal WAR in two versions, one for Tomcat and one for Weblogic, which were based on the corresponding archetypes.
Using a process model with a Process Interface defined that is exposed as a dynamic SOAP endpoint, I get different behavior on Weblogic vs. Tomcat.
To be more precise, on Tomcat I can start a process instance by sending a SOAP envelope to /services/soap/default/MyProcess/ProcessServiceHttpBasicAuth with username/password as HTTP basic auth parameters in the HTTP header.
When I deploy the same model on Weblogic and send the same SOAP request, I always get a HTTP 401 response saying that the user is not authorized.
Something that I noticed on the server log is that one of the Weblogic server threads actually says that the user "motu" has tried to login unsuccessfully 5 times and that the account will now be locked for 30 minutes!? This does not seem to be coming from Stardust, but how would Weblogic know about the "motu" user ...?
I can still logon to the Stardust portal with that user.
[Updated on: Wed, 13 February 2013 22:49]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01799 seconds