-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.1.X, 7.2.X
-
Fix Version/s: 7.1.10 DXP FP15, 7.1.X, 7.2.10 DXP FP1, 7.2.X, 7.2.1 CE GA2, Master
-
Component/s: Portal Configuration > Portal Instances
-
Branch Version/s:7.2.x, 7.1.x
-
Backported to Branch:Committed
-
Fix Priority:4
-
Sprint:U&SM | S03 Sprint 2, U&SM | S03 Sprint 3
-
Git Pull Request:
Summary:
The "Virtual Host" and "Mail Domain" fields have a validation check during the initial creation. If we create a proper virtual instance with valid "Virtual Host" and "Domain Names", anything can be inputted into those fields after editing.
The validator will permit the formula of (1) alphanumeric unaccented characters [0-9a-zA-Z], hyphen, and underscore + (2) at least two alphabet characters for the top-level domain (TLD).
Valid | Invalid |
---|---|
liferay.com | liferay.c |
hello.co | hello |
liferay.co.jp | ライフレイ.jp |
Steps to Reproduce:
1. Add a Virtual Instance with valid Virtual Host and Mail Domain > Save
Virtual Host: lifer.ay Mail Host: life.ray
2. Edit the same Virtual Instance's Virtual host and Mail Domain with things that would otherwise fail the initial validation
Virtual Host: lifera.y Mail Host: サイト
3. Change entries to "test" > Save
Expected Results:
Validation kicks in, so we're unable to save changes and a fail message
Actual Results:
We're able to save invalid hostnames with a success message
Environment:
Tomcat 9.0.17 + MySQL 5.7 + Portal 7.2.x GIT ID:
0c346b627514af36785fd8f06befb86f10a584a8
Base Branch Commit: c8164d415304a63bfe7e8370a726fd44596c625e
- is related to
-
LPS-98224 Unable to see details of unexpected exceptions on new instances creation
- Closed