SEAM working with Windows AD, but not creating Credential Cache

[Tyson Oswald]

I recenly got SEAM working with Windows 2003  on Solaris 9, I can login which is great.  My only concern is that the creential cache is not created in /tmp.  This leads me to believe that there is an problem somewhere.  I would like to resolve this before we roll this out to our other servers.  
 
Here is the debugging info from pam
 
Jan 12 07:46:41 snoopy sshd[23092]: [ID 655841 local6.debug] PAM-KRB5 (auth): pam_sm_authenticate flags=1
Jan 12 07:46:41 snoopy sshd[23092]: [ID 549540 local6.debug] PAM-KRB5 (auth): attempt_krb5_auth: start: user='cbrown'
Jan 12 07:46:41 snoopy sshd[23092]: [ID 179272 local6.debug] PAM-KRB5 (auth): attempt_krb5_auth: krb5_get_init_creds_password returns: SUCCESS
Jan 12 07:46:41 snoopy sshd[23092]: [ID 833335 local6.debug] PAM-KRB5 (auth): attempt_krb5_auth returning 0
Jan 12 07:46:41 snoopy sshd[23092]: [ID 914654 local6.debug] PAM-KRB5 (auth): pam_sm_auth finalize ccname env, result =0, env ='KRB5CCNAME=FILE:/tmp/krb5cc_106', age = 0, status = 0
Jan 12 07:46:41 snoopy sshd[23092]: [ID 525286 local6.debug] PAM-KRB5 (auth): end: Success

Can anyone else see as to why it won't create the cc in /tmp?  I definately can create files in /tmp.
 
thanks,
Tyson