Non-default Quality of Protection?

2013-11-12 Thread Tomas Kuthan
Hi all, I am confuzzled about usefulness of the QOP concept in GSS-API. RFC 2743 states, that using non-default QOP is a mechanism specific, non-portable construct. RFC 4121 says, that applications using different QOP than default are not guaranteed portability and interoperability. It also

Re: Non-default Quality of Protection?

2013-11-12 Thread Benjamin Kaduk
On Tue, 12 Nov 2013, Tomas Kuthan wrote: Hi all, I am confuzzled about usefulness of the QOP concept in GSS-API. RFC 2743 states, that using non-default QOP is a mechanism specific, non-portable construct. RFC 4121 says, that applications using different QOP than default are not

Re: Non-default Quality of Protection?

2013-11-12 Thread Tomas Kuthan
On 11/12/13 04:29 PM, Benjamin Kaduk wrote: On Tue, 12 Nov 2013, Tomas Kuthan wrote: Hi all, I am confuzzled about usefulness of the QOP concept in GSS-API. RFC 2743 states, that using non-default QOP is a mechanism specific, non-portable construct. RFC 4121 says, that applications using

HTTP binding of Kerberos GSS API - Behaviour with Mutual Auth

2013-11-12 Thread Arpit Srivastava
Hi, I have mutual authentication enabled at AD. I am also requesting mutual authentication for the security context in my code at client side. I am generating a token using init_sec_context and sending it with negotiate in authorization header of HTTP requests (AP-REQ). I was expecting that,