On 12/18/2014 02:02 PM, Xie, Hugh wrote:
> I am getting "Wrong principal in request" error on gss_accept_sec_context()
> on one host but does not on another. I verified /etc/hosts, both host conform
> to this format
>
> # Default /etc/hosts file
> 127.0.0.1 localhost.localdomain localhost
* What do "hostname" and "hostname -f" say on each host?
The working on are using "host1.bankofamerica.com" the non working one has
"host2.site123.baml.com". "hostname" and "hostname -f" returns same string on
both hosts.
In the KRB5_CONFIG of both hosts, default_realm is set to
COMMON.BANKOFA
When you try to connect to the non-working server on the client, what
service ticket appears in the cache as reported by klist? How does this
compare to the entries in the keytab on the non-working server?
On 12/19/2014 11:50 AM, Xie, Hugh wrote:
>
> * What do "hostname" and "hostname -f" say on
Can someone tell me if the NEGOEX made it to the MIT trunk? All information I
can google was back to 2012 where Luke Howard has an implementation of the MIT
code base.
regards
-peter
Kerberos mailing list Kerberos@mit.edu
https://m
We are using the same account on both hosts the Principal in the keytab is
"mya...@common.bankofamerica.com"
Klist return service principals are the same
"krbtgt/common.bankofamerica@common.bankofamerica.com" on both host
-Original Message-
From: Greg Hudson [mailto:ghud...@mit.edu
On the client side two ticket shows up for either when connects for either
hosts the krbtgt/COMMON.BANKOFAMERICA.COM @ COMMON.BANKOFAMERICA.COM
The service ticket on the clients has the principal of:
HTTP/host1.bankofamerica.com @ COMMON.BANKOFAMERICA.COM
HTTP/host2.site123.baml.com @ COMMON.BANKO
