Hide Forgot
Date of First Response: 2010-02-09 08:50:43 project_key: SOA The security service implementation used in the jUDDI console is unable to retrieve an authToken from a remote server as defined in the client config file. At this time it's not possible to pinpoint the cause because the implementation puts only a warning to the log when it is unable to retrieve the token. IMHO the problem might be connected with the manner how the class handles configuration loading. For the stack see attached server log.
Attachment: Added: server.log
This is a candidate for SOA 5.1.0, Not Committed.
Link: Added: This issue related SOA-2567
The NPE was fixed in the juddi-3.0.4 release: https://issues.apache.org/jira/browse/JUDDI-420 However when fixing this is was discover something else was broken, I opened a new jira for that one: SOA-2567
Writer: Added: dlesage
Verified on ER6. Note: It's necessary to click the new subscription button to show the configured nodes.
Temporarily reopening to update release note information.
Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/SOA-1935 The security service implementation used in the jUDDI console was unable to retrieve an authToken from a remote server that was defined in the client configuration file. This was due to a bug in jUDDI that was resolved by upgrading that component to a newer version. (Note that it is necessary to click the New Subscription button to show the configured nodes.)