×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I contacted IBM support, and they said I have to explicitly add the fully-qualified name to every browser. They didn't say why the short name works without doing anything special.
From: Justin Taylor
Sent: Wednesday, September 12, 2018 4:35 PM
To: WEB400 (web400@xxxxxxxxxxxx) <web400@xxxxxxxxxxxx>
Subject: Fully-qualified name & Kerberos
I use Kerberos authentication for my Apache server that hosts my CGI apps. The URL's use the unqualified hostname (e.g.
http://myHost/<
http://my_host/>).
I'm now trying to set up HTTPS. I already have an SSL cert, but the tricky part is that the cert is for myHost.domainName.com (I didn't do it, and I didn't have any say in the matter). If I try
https://myHost/<
https://my_host/>, it gives me a cert error, due to the name mismatch. If I try
https://myHost.domainName.com<
https://my_host.domain_name.com>, FF gives "Authentication Required", while Chrome & IE prompt for a login.
I tried the fully-qualified name in iNav, and Kerberos worked perfectly.
Any thoughts?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
