Bug 793571 (JBEPP-650)
| Summary: | GTNPORTAL-1673 make UI validation regular expressions configurable by users | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Gary Hu <garyhu2> |
| Component: | Portal | Assignee: | claprun <claprun> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0.GA, 5.0.1.GA, 5.1.0.GA, 5.1.1.GA | CC: | chris.laprun, claprun, jmorgan, mmiura, mweiler, mzottner, plamarque, theute, tkobayas |
| Target Milestone: | --- | ||
| Target Release: | 5.2.1.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-650 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Several fields requiring user names were previously validated using hardcoded logic, which prevented users from easily changing what user name formats were acceptable for their requirements. The fix implements ExpressionValidator, which permits user name validation changes without having to customize the source code. The validator allows users to specify the format required for valid user names, which overrides the default field validation present in the portal.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-02-09 19:23:00 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Gary Hu
2010-11-19 18:11:56 UTC
Link: Added: This issue Cloned to GTNPORTAL-1673 Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes] Set Release Notes Not Yet Documented because this issue is a Customer-initiated issue. When the issue is fixed, all issues with Helpdesk ticket references *must* have a release note provided, and included in the Release Notes document. Release Notes Docs Status: Added: Not Yet Documented Labels: Added: EPP_5_2_1_Candidate EPP_6_0_0_Candidate Hi everyone! I badly need this one for a customer that uses emails as user names. A customizable/central/extensible regex and error message for the validation of usernames and passwords would be enough (4 elements). At the moment the validation texts seem to be distributed in different properties files. /GATEIN/deploy/gatein.ear/02portal.war/WEB-INF/classes/locale/portal/webuiXXX.properties -> UIGroupMembershipForm.msg.Invalid-char -> ResourceValidator.msg.Invalid-char -> UIGroupMembershipForm.msg.Invalid-char /GATEIN/deploy/gatein.ear/02portal.war/WEB-INF/classes/locale/portal/servicesXXX.properties -> IdentifierValidator.msg.invalid-char -> NameValidator.msg.invalid-char best regards, Marc Labels: Removed: EPP_5_2_1_Candidate EPP_6_0_0_Candidate Added: EPP_5_2_1_Candidate Labels: Removed: EPP_5_2_1_Candidate Needs to be tested more thoroughly. Release Notes Text: Added: Several fields requiring user names where previously validated using hardcoded logic, thus preventing users from easily changing which user names were acceptable for their requirements. A new configurable validator has been implemented that can be configured by users without having to modify the source code thus allowing users to more easily change the format for valid user names. this change seem to have created an incompatibility with eXo WCM. wcm 2.3.6 does not work properly on top of EPP 5.2 ER1 : https://jira.exoplatform.org/browse/SPUB-154 It's blocker for SP 5.2.1 Changes have been made to remediate the issue. A new version of EPP 5.2.1 should be available soon.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Several fields requiring user names where previously
validated using hardcoded logic, thus preventing users from easily changing
which user names were acceptable for their requirements. A new configurable
validator has been implemented that can be configured by users without having
to modify the source code thus allowing users to more easily change the format
for valid user names.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,6 +1 @@
-Several fields requiring user names where previously
+Several fields requiring user names were previously validated using hardcoded logic, which prevented users from easily changing what user name formats were acceptable for their requirements. The fix implements ExpressionValidator, which permits user name validation changes without having to customize the source code. The validator allows users to specify the format required for valid user names, which overrides the default field validation present in the portal.-validated using hardcoded logic, thus preventing users from easily changing
-which user names were acceptable for their requirements. A new configurable
-validator has been implemented that can be configured by users without having
-to modify the source code thus allowing users to more easily change the format
-for valid user names.
|