Bug 1351217 - FQDN checking introduced by SSO should be case-insensitive or engine-setup should lower-case Host FQDN
Summary: FQDN checking introduced by SSO should be case-insensitive or engine-setup sh...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: AAA
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.0.1
: 4.0.1.1
Assignee: Ravi Nori
QA Contact: Gonza
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-29 13:41 UTC by Ralf Schenk
Modified: 2016-08-18 07:07 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-18 07:07:11 UTC
oVirt Team: Infra
Embargoed:
mperina: ovirt-4.0.z?
rule-engine: planning_ack+
mperina: devel_ack+
rule-engine: testing_ack?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 59949 0 None MERGED aaa: FQDN checking introduced by SSO should be case-insensitive 2020-06-05 14:47:14 UTC
oVirt gerrit 59954 0 None MERGED aaa: FQDN checking introduced by SSO should be case-insensitive 2020-06-05 14:47:14 UTC

Description Ralf Schenk 2016-06-29 13:41:15 UTC 
Description of problem:
After upgrading ovirt-engine to 4.0 I wasn't able to log into web-ui via URL 
https://engine-mciii.mydomain.com

Error page stated: "The client is not authorized to request an authorization. It's required to access the system using FQDN."


Version-Release number of selected component (if applicable): 4.0.0.6

How reproducible: Try to access web UI where Hosted Engine Configuration contains case-mixed Host FQDN which is fully resolvable by DNS i.e.: engine-mcIII.mydomain.com

Steps to Reproduce:
1. Setup Engine with case-mixed or upper-case characters in Host FQDN
2. Try to login via URL

Actual results:
No login possible, Error page states "The client is not authorized to request an authorization. It's required to access the system using FQDN."

Expected results:
Login possible

Additional info:
1. Could be solved by a case-insensitive check of Engine Host FQDN to URL Hostname.
2. As an alternative lowercase user input in setup for Host FQDN
Comment 1 Pavel Stehlik 2016-08-18 07:07:11 UTC 
Closing due to capacity, if still happens, please reopen.
Note You need to log in before you can comment on or make changes to this bug.