We are facing similar problem? Any new ideas how to overcome this? Tried
also scenario 1 from 'Real-life Tips on Configuring Kerberos for
Authentication in Access Manager | Novell User Communities'
with no luck since

sAMAccountName = User

NAM ldapsearch User@domain.com

Both creating a custom authentication class or adding a new attribute
containing user@domain.com for all the users in AD seem quite a drastic
solutions for a small problem.

sremars;1971953 Wrote:
> Thanks you for the reply,
> In my case, ecause sAMAccountName is not equal to the UPN or the CN, I
> must rewrite the Kerberos Class. Where I can find the source of the
> current Kerberos Class ?
> Thanks
> Stephane

vesapi's Profile: http://forums.novell.com/member.php?userid=73631
View this thread: http://forums.novell.com/showthread.php?t=409805