Re: Fully-qualified name & Kerberos

[Bradley Stone <bvstone@xxxxxxxxx>]

The SSL certificate has to be created set for the host you are using,
either directly or using SAN (Subject Alternative Name).  It looks like you
have myhost set up somewhere to resolve to the same IP as
myhost.domainname.com.


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #22 <https://www.bvstools.com/mailtool.html>: Cost
starting at under $300 a year per partition!

On Wed, Sep 12, 2018 at 4:35 PM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

> 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 is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
> list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/web400.