Isn't Apple's provided Kerberos just MIT Kerberos? Is it modified in some
way? The only difference that has been apparent to me so far is the
location of the config file...and I guess the fact that each machine has a
"local" Kerberos KDC in addition to whatever Kerberos realm you join it to
(or make it a KDC for).
At any rate, cosign worked out of the box on the development machine. No
problems at all.
Kevin Horn
On Thu, Mar 12, 2009 at 8:23 PM, Wesley Craig <[email protected]> wrote:
> On 11 Mar 2009, at 15:34, Kevin Horn wrote:
>
>> It looks like the cosign cgi calls kerberos, which tries to locate open
>> directory, which then goes into CoreFoudation and passes beyond my
>> understanding.
>>
>> I should also point out that I can authenticate just fine against kerberos
>> using kinit/kadmin/etc so I don't understand what's going on here exactly.
>>
>
> The Kerberos API that Apple provides isn't necessarily compatible with the
> API that cosign is expecting. I'm not aware of anyone who has made cosign
> work with Apple's provided Kerberos. Which is not to say that it can't be
> done, but it will probably involve some debugging.
>
> :wes
>
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
