PR: https://github.com/ManageIQ/manageiq/pull/5812
GT, I'm trying to draft doc text for this, but I'm finding it hard to follow. What we need is: What caused the problem? What was the consequence? What fixed it?
Marianne, I'll try my best to summarize: | What caused the problem? | Validation for external authentication prevented the customer from entering a top-level domain under IPA server domain. | What was the consequence? | They couldn't configure external authentication | What fixed it? | We relaxed the validation to allow top-level domains. Let me know if you have any further questions. Tim
# vmdb # cat VERSION 5.5.2.2 # appliance_console # Then Enter, 10, Enter Configure External Authentication (httpd) IPA Server Parameters: Enter the IPA Server Hostname: test1.domain Enter the IPA Server Domain: domain Enter the IPA Server Realm: |DOMAIN| Enter the IPA Server Principal: |admin| Enter the IPA Server Principal Password: *** External Authentication (httpd) Configuration: IPA Server Details: Hostname: test1.domain Domain: domain Realm: DOMAIN Naming Context: dc=domain Principal: admin Proceed? (Y/N): ========================================= So it now accepts the TLD as a domain.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:0159