| Summary: | RTG client-only configuration does not configure the URL of server | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | Installer | Assignee: | Thomas Hauser <thauser> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Len DiMaggio <ldimaggi> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 GA | CC: | atangrin, soa-p-jira |
| Target Milestone: | ER4 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jiri Pechanec
2013-10-02 05:59:35 UTC
Found the issue. This will be in subsequent rebuilds. A question: does it make sense to have the validation we do on this password? - At least 8 chars - At least one numeric char - At least one "special" char I was thinking because the RTGov server will be user configured outside of the installer, that this validation probably doesn't make sense and can cause issues with the user not being able to enter the password they have given their RTGov server. I have no strong opinion about this - does installation of rtgov server with password configuration enforce the same rules? Currently all passwords in the installer enforce this rule. Except for the DB ones, which obviously cannot be constrained in this way. Just thought I'd make note of that. Verified in ER4 04-Oct-2013 04:44 |