On Mon, May 19, 2008 at 10:25 AM, AndrePra <[EMAIL PROTECTED]> wrote:
> Ok, I resolved the problem by myself. The problem was due that in my network
> the jifsDomain is not recognizable with his name. I don't know if this is an
> error in domain configuration, but changing the jcifsDomain with the IP
> everything work.
> To resolve the problem i put the project in debug and I saw that throws an
> exception in the class JCIFSSpnegoAuthenticationHandler
>
>> try {
>> // proceed authentication using jcifs
>> synchronized (this) {
>> this.authentication.reset();
>>
>> this.authentication.process(spnegoCredentials.getInitToken());
>> principal = this.authentication.getPrincipal();
>> nextToken = this.authentication.getNextToken();
>> }
>> } catch (jcifs.spnego.AuthenticationException e) {
>> throw new BadCredentialsAuthenticationException();
>> }
>
> I suggest to trace the message of the catched exception.
Could you please add an issue on this in JIRA please ?
> Now I can authenticate the user with NTLM token because the token i received
> is NTLMSSP. How can i force the Kerberos authenication? Putting NTLM allowed
> to false doesn't work.
Putting a false in the NTLM allowed flag will only reject NTLM token
as valid authentication token. The user stills have to continue to
fill the login form.
As Michael suggest have a look at any DNS issue using only FQDN. I see
that you use casserver in the passed token in your log which is not a
FQDN.
If the problem persist, you should have a closer look at the client
configuration.
Regards,
--
Arnaud Lesueur
LinkedIn: http://www.linkedin.com/in/lesueur
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
