Bug 793319 (JBEPP-402)
| Summary: | Remove IP addresses from picketlink msad example config files | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Martin Weiler <mweiler> |
| Component: | Portal | Assignee: | Nobody <nobody> |
| Status: | VERIFIED --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0.GA | CC: | boleslaw.dawidowicz, epp-bugs, theute |
| Target Milestone: | --- | ||
| Target Release: | 5.2.1.ER02 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-402 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
It was discovered that the Microsoft Active Directory (MSAD) configuration files (<filename>picketlink-idm-msad-config.xml</filename> and <filename>picketlink-idm-msad-readonly-config.xml</filename>) contained a providerURL property with an IP address specified. The IP address was interpreted by customers as required and mandatory, instead of being interpreted as a value that needed to be changed to an IP address used in the customer's implementation. The fix replaces the numerical IP address with replaceable values that are more prescriptive to users, which corrects the originally reported issue.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Task | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Martin Weiler
2010-08-10 08:55:04 UTC
Requires merge from: https://fisheye.jboss.org/changelog/gatein/portal/trunk?cs=5762 Release Notes Docs Status: Added: Not Yet Documented Release Notes Text: Added: CAUSE: CONSEQUENCE: FIX: RESULT:
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:
==CUSTOMER FACING ISSUE REQUIRES RELEASE NOTE==
CAUSE:
CONSEQUENCE:
FIX:
RESULT:
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,9 +1,13 @@
==CUSTOMER FACING ISSUE REQUIRES RELEASE NOTE==
CAUSE:
+Fixed IP addresses as example in configuration files
CONSEQUENCE:
+Confusion as what needs to be changed and what needs to remain the same
FIX:
+Replaced IP addresses with bracket style template to show what needs to be replaced
-RESULT:+RESULT:
+Less confusion
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,13 +1 @@
-==CUSTOMER FACING ISSUE REQUIRES RELEASE NOTE==
+It was discovered that the Microsoft Active Directory (MSAD) configuration files (<filename>picketlink-idm-msad-config.xml</filename> and <filename>picketlink-idm-msad-readonly-config.xml</filename>) contained a providerURL property with an IP address specified. The IP address was interpreted by customers as required and mandatory, instead of being interpreted as a value that needed to be changed to an valid IP address used in the customer's implementation. The fix replaces the numerical IP address with replaceable values that are more prescriptive to users, which corrects the originally reported issue.-
-CAUSE:
-Fixed IP addresses as example in configuration files
-
-CONSEQUENCE:
-Confusion as what needs to be changed and what needs to remain the same
-
-FIX:
-Replaced IP addresses with bracket style template to show what needs to be replaced
-
-RESULT:
-Less confusion
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 +1 @@
-It was discovered that the Microsoft Active Directory (MSAD) configuration files (<filename>picketlink-idm-msad-config.xml</filename> and <filename>picketlink-idm-msad-readonly-config.xml</filename>) contained a providerURL property with an IP address specified. The IP address was interpreted by customers as required and mandatory, instead of being interpreted as a value that needed to be changed to an valid IP address used in the customer's implementation. The fix replaces the numerical IP address with replaceable values that are more prescriptive to users, which corrects the originally reported issue.+It was discovered that the Microsoft Active Directory (MSAD) configuration files (<filename>picketlink-idm-msad-config.xml</filename> and <filename>picketlink-idm-msad-readonly-config.xml</filename>) contained a providerURL property with an IP address specified. The IP address was interpreted by customers as required and mandatory, instead of being interpreted as a value that needed to be changed to an IP address used in the customer's implementation. The fix replaces the numerical IP address with replaceable values that are more prescriptive to users, which corrects the originally reported issue.
|