I have one WebLogic server that needs to access a web service in one iis server and this web server is protected by Kerberos. My code works fine in the development environment where kerberos and ntlm are both activated (but the mechanism choosen is kerberos). In production environment, ntlm is disabled (I was told that this is the main difference beetween the two environments). Now, what happens is that, in production mode instead of getting an Authorization Header: Negociate, I receive an Authorization Header: Kerberos and, of course, I receive from the code one
Now, the guys here in my company (the iis administrators) know nothing about kerberos (I think the've configured the iis/kerberos/AD following some kind of next, next, next install, if you know what I mean).
The final question is: How can I workaround this exception??
Just adding some more info on the subject
In the code posted above,
In Production env.,
there's no token!!!
thanks for any light!!!
Manuel Leiria<br /> <br />--------------<br />Peace cannot be kept by force; it can only be achieved by understanding. <br /> Albert Einstein
subject: Consuming a .NET kerberized web service using the spnego.sourceforge.net open source library