| Summary: | Logout link is missing in the jUDDI console | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Locker <jlocker> | ||||
| Component: | jUDDI - within SOA | Assignee: | Kurt Stam <kurt.stam> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.0.0 ER5 | CC: | kurt.stam | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.2.0 GA, 5.2.0.ER4 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-1752 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-10-05 18:11:37 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
Jiri Locker
2009-12-22 11:28:31 UTC
The tests cases use an Admin user and an ordinary user. It's very annoying from a test standpoint to have to restart the server each time i want to switch user (between admin and ordinary user). This is the reason the Jira was marked as a test blocker. Anyway, maybe there is a reasonble work around, in which case the test blocker status can be removed. Potential Work Around from Darran: <darran> ping mharvey - could JMX be used to invalidate the web session for that testing? <darran> mharvey, each web app has a Manager MBean, one method listSessionIds shows a list of active sessions and the expireSession method can be used to expire individual sessions - just wondering if this would give the same behaviour as logout Workaround confirmed. Affects Testing: Removed: [Blocks Testing] This was triaged for SOA 5.1. It is not a feature request. It's a bug and we will not do it for SOA 5.1.0 This is related to : https://issues.apache.org/jira/browse/JUDDI-297, targeted for jUDDI-3.1.1. Applied same fix as for juddi-297, and added a link the logout.jsp which invalidates the session and uddi token. Upgraded to uddi-portlets 3.1.1. Attachment: Added: patch-SOA-1752.txt Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/SOA-1752 There was no easy way to log out of the JUDDI console and log back in. A logout link has now been added. |