| Summary: | Character encoding incorrect with SSO enabled | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Martin Weiler <mweiler> | ||||
| Component: | Portal | Assignee: | Thomas Heute <theute> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.1.0.GA | CC: | epp-bugs | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.1.1.DEV01 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-896 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
EPP 5.1
CAS, JOSSO, OpenSSO integration as documented in http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/5.0/html/Reference_Guide/sect-Reference_Guide-SSO_Single_Sign_On.html
|
|||||
| Last Closed: | 2011-04-20 11:39:41 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
Martin Weiler
2011-04-19 11:13:13 UTC
Link: Added: This issue Cloned from JBEPP-387 Link: Removed: This issue Cloned from JBEPP-387 Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Not Yet Documented Release Notes Text: Removed: CAS integration had issues with incorrect character encoding Added: SSO integration had issues with incorrect character encoding Help Desk Ticket Reference: Removed: https://enterprise.redhat.com/issue-tracker/1030703 Added: https://na7.salesforce.com/500A00000079kJi Steps to Reproduce: Removed: 1. Setup EPP 4.3 with CAS 2. Deploy the JSPHelloUser sample portlet 3. Try the sample with a Hindi character Added: 1. Setup EPP 5.1 with CAS/JOSSO/OpenSSO 2. Deploy the JSPHelloUser sample portlet 3. Try the sample with a Latin2 character Attachment: Added: JBEPP-896.patch Link: Added: This issue relates to JBEPP-898 Patch applied in Product branch, 1.0 branch and trunk Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Removed: SSO integration had issues with incorrect character encoding Added: SSO integration had issues with incorrect character encoding, the character encoding of the request is now specified. Affects: Added: [Release Notes] Release Notes Text: Removed: SSO integration had issues with incorrect character encoding, the character encoding of the request is now specified. Added: Cause: The Single Sign On (SSO) AbstractLogoutFilter in EPP would read request parameters before setting the character encoding. Consequence: When a form was submitted with non-UTF-8 characters (while SSO was enabled) the values could be garbled on output. Fix: An upgrade of the SSO component to version 1.0.2-epp-GA (which includes a patch to the AbstractLogoutFilter code) resolves this issue. Result: Non-UTF-8 characters are now specified correctly. Release Notes Text: Removed: Cause: The Single Sign On (SSO) AbstractLogoutFilter in EPP would read request parameters before setting the character encoding. Consequence: When a form was submitted with non-UTF-8 characters (while SSO was enabled) the values could be garbled on output. Fix: An upgrade of the SSO component to version 1.0.2-epp-GA (which includes a patch to the AbstractLogoutFilter code) resolves this issue. Result: Non-UTF-8 characters are now specified correctly. Added: The Single Sign On (SSO) AbstractLogoutFilter in JBoss Enterprise Portal Platform would read request parameters before setting the character encoding. When a form was submitted with non-UTF-8 characters (while SSO was enabled) the values could be garbled on output. An upgrade of the SSO component to version 1.0.2-epp-GA (which includes a patch to the AbstractLogoutFilter code) resolves this issue and Non-UTF-8 characters are now specified correctly. |