understand my problem
error : kinit(v5) : KRB5 error code 52 while getting initial credentials
You have told about going for new version of Kerberos.
Let me confirm :
I tried a pilot server in KDC domain XX.COM http://XX.COM. i got a
keytab and installed in the pilot server. Then i did
.
i copied into Apache folder and executed the command.
kinit -t /usr/local/apache/test03keytab HTTP/[EMAIL PROTECTED]
password:
error : kinit(v5) : KRB5 error code 52 while getting initial credentials
Please help me understand what is this erro.. is it some issue with
domain
system is the server?
What system is the client?
2) i somehow managed to get a keytab . i copied into Apache folder and
executed the command.
kinit -t /usr/local/apache/test03keytab HTTP/[EMAIL PROTECTED]
password:
error : kinit(v5) : KRB5 error code 52 while getting initial
.
kinit -t /usr/local/apache/test03keytab HTTP/[EMAIL PROTECTED]
password:
error : kinit(v5) : KRB5 error code 52 while getting initial credentials
Please help me understand what is this erro.. is it some issue with
domain
mapping configuration in krb5.conf file? i am
from the KDC of XX.COM ( my server in co.yy)
ktpass -princ HTTP/[EMAIL PROTECTED]
2) i somehow managed to get a keytab .
i copied into Apache folder and executed the command.
kinit -t /usr/local/apache/test03keytab HTTP/[EMAIL PROTECTED]
password:
error : kinit(v5) : KRB5 error code 52 while
the KDC of XX.COM ( my server in
co.yy)
ktpass -princ HTTP/[EMAIL PROTECTED]
2) i somehow managed to get a keytab . i copied into Apache folder and
executed the command.
kinit -t /usr/local/apache/test03keytab HTTP/[EMAIL PROTECTED]
password:
error : kinit(v5) : KRB5 error code 52 while
? (Windows? Linux? other?)
What system is the server?
What system is the client?
2) i somehow managed to get a keytab . i copied into Apache folder and
executed the command.
kinit -t /usr/local/apache/test03keytab HTTP/[EMAIL PROTECTED]
password:
error : kinit(v5) : KRB5 error code 52
.
kinit -t /usr/local/apache/test03keytab HTTP/[EMAIL PROTECTED]
password:
error : kinit(v5) : KRB5 error code 52 while getting initial credentials
Please help me understand what is this erro.. is it some issue with domain
mapping configuration in krb5.conf file? i am using kerberos
] To: [EMAIL
PROTECTED] CC: [EMAIL PROTECTED]; kerberos@mit.edu Subject: Re: kinit: KRB5
error code 52 while getting initial credentials On Wed, Jul 11, 2007 at
01:10:19AM +, Ron Bass II wrote:Thanks for the update Will. I'll
look into Solaris 10... Note that there have been a number
On Wed, Jul 04, 2007 at 05:56:56PM +, Ron Bass II wrote:
I'm getting the following error on a Solaris 8 machine: kinit: KRB5
error code 52 while getting initial credentials
So far my analysis shows this error to indicate the following: 0x34 -
KRB_ERR_RESPONSE_TOO_BIG - Too much data
on Solaris 10 support TCP
Hooshang
Kerberos experts,
I am using SEAM 1.01 on Solaris 9 and am authenticating to AD. When others try
they fail the login with the KRB5 error code 52 error. I read that this has
something to do with UDP packet size and to try TCP. Is there a way
Hooshang
Kerberos experts,
I am using SEAM 1.01 on Solaris 9 and am authenticating to AD. When others try
they fail the login with the KRB5 error code 52 error. I read that this has
something to do with UDP packet size and to try TCP. Is there a way in SEAM to
have it use TCP rather
the login with the KRB5 error code 52 error.
I read that this has something to do with UDP packet size and to try
TCP. Is there a way in SEAM to have it use TCP rather then UDP, or
to try UDP then TCP is that fails? I was hoping there was a
configuration parameter in krb5.conf.
thanks
Kerberos experts,
I am using SEAM 1.01 on Solaris 9 and am authenticating to AD. When others try they
fail the login with the KRB5 error code 52 error. I read that this has something to
do with UDP packet size and to try TCP. Is there a way in SEAM to have it use TCP
rather then UDP
[EMAIL PROTECTED] (Uli Schröder) writes:
...
As usual a new problem came up after that. I cannot compile pam_krb5
anymore. Maybe I have to use different linking options.
Interesting. What do you need to change? Does it work okay with a
different set of linking options?
I couldn't
[EMAIL PROTECTED] writes:
doesn't come up with any messages. Still if I activate the module for pam.d,
authentication doesn't work. I get the following messages in my syslog:
Jun 12 10:03:21 rh9test login: PAM unable to
dlopen(/lib/security/$ISA/pam_krb5.so)
Jun 12 10:03:21 rh9test login:
...
doesn't come up with any messages. Still if I activate the
module for
pam.d, authentication doesn't work. I get the following
messages in my
syslog:
Jun 12 10:03:21 rh9test login: PAM unable to
dlopen(/lib/security/$ISA/pam_krb5.so)
Jun 12 10:03:21 rh9test login: PAM
Ken Raeburn [EMAIL PROTECTED] schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
...
Nevertheless if I do a kinit for my my normal account it fails with
error code 52. No change between krb5-1.2.7 and krb5-1.3.
Is it saying KRB5 error code 52 exactly? That shouldn't be in the
source code
[EMAIL PROTECTED] (Uli Schröder) writes:
I had another kinit in the my path. I wasn't aware of that. I thought I
had deleted all the old stuff. Now the new kinit workes great. I can use
kinit with my own account. No more error 52! :)
Good, I'm glad to hear it.
As usual a new problem came up
Hi all together! Hi Ken!
Yep, client-side TCP support wasn't in that release. The
upcoming release from MIT will include it.
Is that already included in the snapshot or 1.3-beta versions on the
internet? Did MIT announce an estimated time for a release?
Yes, it's been in the 1.3
it fails with
error code 52. No change between krb5-1.2.7 and krb5-1.3.
Is it saying KRB5 error code 52 exactly? That shouldn't be in the
source code for the 1.3 snapshot. The error message is now Response
too big for UDP, retry with TCP, and shouldn't be displayed unless
the server sends
Hi folks,
I have a problem authenticating my RedHat 9 against Active Directory.
I'm running the MIT implementation of kerberos.
When I run kinit for my testuser it works fine. The testuser ist just a
member of the domain with read access to the directory. No other groups
or permissions. When
Hi folks,
I have a problem authenticating my RedHat 9 against Active Directory.
I'm running the MIT implementation of kerberos.
When I run kinit for my testuser it works fine. The testuser ist just a
member of the domain with read access to the directory. No other groups
or permissions. When
When I run kinit for my testuser it works fine. The testuser ist just a
member of the domain with read access to the directory. No other groups
or permissions. When I try to do a kinit for my own account with all its
group memberships, etc., I just get the error code 52. I read on the
Hi Ken!
When I run kinit for my testuser it works fine. The
testuser ist just
a
member of the domain with read access to the directory. No
other groups
or permissions. When I try to do a kinit for my own account
with all its
group memberships, etc., I just get the error code
Uli Schröder [EMAIL PROTECTED] writes:
Yep, client-side TCP support wasn't in that release. The
upcoming release from MIT will include it.
Is that already included in the snapshot or 1.3-beta versions on the
internet? Did MIT announce an estimated time for a release?
Yes, it's been in the
l9phan1 == l9phan1 [EMAIL PROTECTED] writes:
l9phan1 I got the following error message when using kinit
l9phan1 command: kinit (v5): krb5 error code 52 while getting
l9phan1 initial credentials.
When a user is in too many groups, the Windows KDC requests that the
client use TCP
27 matches
Mail list logo
