Skip to content

Commit 6df1d7e

Browse files
committed
Mention Channel Bindings support in the README
Signed-off-by: Simo Sorce <simo@redhat.com>
1 parent 4fdca19 commit 6df1d7e

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

README.rst

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -241,3 +241,26 @@ If you are having difficulty we suggest you configure logging. Issues with the
241241
underlying GSSAPI libraries will be made apparent. Additionally, copious debug
242242
information is made available which may assist in troubleshooting if you
243243
increase your log level all the way up to debug.
244+
245+
Channel Bindings
246+
----------------
247+
248+
Optional simplified support for channel bindings is available, but limited to
249+
the 'tls-server-end-point' bindings type (manual construction of different
250+
channel bindings can be achieved using the raw API). When requesting this kind
251+
of bindings python-cryptography must be available as request-gssapi will try
252+
to import its x509 module to process the peer certificate.
253+
254+
.. code-block:: python
255+
256+
>>> import requests
257+
>>> from requests_gssapi import HTTPSPNEGOAuth
258+
>>> gssapi_auth = HTTPSPNEGOAuth(channel_bindings='tls-server-end-point')
259+
>>> r = requests.get("https://windows.example.org/wsman", auth=gssapi_auth)
260+
...
261+
262+
It should be noted that this will not work for connections that are closed on
263+
the initial authentication failure. If the connection is closed, the peer
264+
certificate may be purged from internal data structures and is not available
265+
to extract the ``tls-server-end-point`` value required to complete
266+
authentication.

0 commit comments

Comments
 (0)