| Summary: | jUDDI console's SecurityServiceImpl is unable to retrieve authToken from remote node for clerks. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Marek Baluch <mbaluch> | ||||
| Component: | jUDDI - within SOA | Assignee: | Kurt Stam <kurt.stam> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.0.0 CR1 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.1.0 GA | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-1935 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-02-11 06:20:43 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Marek Baluch
2010-02-08 15:20:30 UTC
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.) |