credentials cache file not created

Bug #507490 reported by David Pavlotzky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
krb5 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: libapache-mod-auth-kerb

Description: Ubuntu 9.10
Release: 9.10

libapache2-mod-auth-kerb:
  Installed: 5.3-5build1
  Candidate: 5.3-5build1
  Version table:
 *** 5.3-5build1 0
        500 http://nl.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Hi,

I am building a SSO intranet solution using the usual LAMP suspects.

I have set the following option in /etc/apache2/conf.d/kerb.conf:

KrbSaveCredentials on

so I can use the credentials to connect to an ActiveDirectory LDAP server.

I have Kerberos working correctly (Explorer is authenticated) and de KRB5CCNAME ($_SERVER['KRB5CCNAME']) is present and contains a filename. The file (the credentials cache) is never created however and cannot be used.

This used to be working on Jaunty but broke in Karmic.

With LogLevel set to debug in Apache I get the following message in /var/log/apache2/error.log:

[Thu Jan 14 12:29:20 2010] [error] [client xxx.x.x.xxx] Cannot store delegated credential (gss_krb5_copy_ccache: An unsupported mechanism was requested (Unknown error))

After some research I found the following:

http://krbdev.mit.edu/rt/Ticket/Display.html?id=6594

wich I believe is the source of this problem.
Could the provided patch be backported?

Pretty please with suger on top of course...

Chuck Short (zulcss)
affects: libapache-mod-auth-kerb (Ubuntu) → krb5 (Ubuntu)
Revision history for this message
Sam Hartman (hartmans) wrote : Re: [Bug 507490] Re: credentials cache file not created

See R23482 in upstream subversion; upstream bug 6594

Chuck Short (zulcss)
Changed in krb5 (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Chuck Short (zulcss) wrote :

This has been added in lucid. This might make a good SRU request.

Regards
chuck

Changed in krb5 (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.