Red Hat Bugzilla – Bug 454876
if you point to sat hostname without FQDN, logging in redirects to Login.do forever
Last modified: 2009-09-10 16:26:33 EDT
Description of problem:
A frustrating behavior of Satellite for first-time users is that when you try to
visit the Satellite in a webbrowser using just the satellite's hostname (e.g.,
http://my-satellite) it will just redirect to the Satellite's front login screen
no matter how many times you attempt to login. You have to use the
fully-qualified domain name to successfully login.
It should be pretty simple to add a rewrite rule in the default httpd config for
Satellite to redirect to the FQDN?
This would make for a more polished first-time experience for Satellite customers.
The origin of the problem was in the cookie generation.
When having satellite "sat.domain.com", created cookie was valid for the whole .sat.domain.com domain (inclusive subdomains). When accessing server only using "sat", domain set for the cookie was ".sat", what is not a valid domain and what's why no cookie was sent in the response. There's no login without a cookie.
Now, no domain is set for the new generated cookie, what causes using of default "host" (sat/sat.domain.com) instead of domain defining cookie validity.
git commit: e9715250fa3d95e562e4357ec712495691e7a66b
Available incomposes since Satellite-5.3.0-RHELx-re20090507.1
this should work as a test..
instead of the additional redhat.com
logs in fine
ok.. recreated this on grandprix 5/7.1 build..
I cant login w/ the FQDN now.. however I can login w/ short name..
something is not right..
I managed to login into grandprix using following addresses:
The same into riverraid and 2 of my satellites.
Anyway, I suggest to open a new BZ, if you have trouble logging in using FQDN.
ok.. will do..
John Mathews and I both ran into similar problems. Some how we got satellite into a state where we could not log in. May be a bad cookie.. who knows..
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.