Help Desk Ticket Reference: https://access.redhat.com/issue-tracker/1233653 project_key: JBEPP The example picketlink config files for MS AD contain a providerURL property with an actual IP: 02portal.war/WEB-INF/conf/organization/picketlink-idm/examples/picketlink-idm-msad-config.xml 02portal.war/WEB-INF/conf/organization/picketlink-idm/examples/picketlink-idm-msad-readonly-config.xml <option> <name>providerURL</name> <value>ldap://192.168.0.12:389</value> </option> This has caused confusion for customers who did not spot the incorrect server IP address when configuring EPP 5 to use with MS AD. If we just include the following providerURL property (which is already in the config files, but commented out), the necessary config change would have been detected easier: <option> <name>providerURL</name> <value>[ldap|ldaps]://[msad-host]:[port]</value> </option>
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.