Add WinKerberos-specific blurb for custom principal.
This commit is contained in:
parent
cd615536b7
commit
bc57f3ab80
|
@ -121,7 +121,7 @@ whom you last ran ``kinit`` or ``kswitch``, or an SSO credential if
|
|||
applicable). However, an explicit principal can be specified, which will
|
||||
cause Kerberos to look for a matching credential cache for the named user.
|
||||
This feature depends on OS support for collection-type credential caches,
|
||||
as well as working principal support in pykerberos (it is broken in many
|
||||
as well as working principal support in PyKerberos (it is broken in many
|
||||
builds). An explicit principal can be specified with the ``principal`` arg:
|
||||
|
||||
.. code-block:: python
|
||||
|
@ -132,6 +132,10 @@ builds). An explicit principal can be specified with the ``principal`` arg:
|
|||
>>> r = requests.get("http://example.org", auth=kerberos_auth)
|
||||
...
|
||||
|
||||
On Windows, WinKerberos is used instead of PyKerberos. WinKerberos allows the
|
||||
use of arbitrary principals instead of a credential cache. Passwords can be
|
||||
specified by following the form ``user@realm:password`` for ``principal``.
|
||||
|
||||
Logging
|
||||
-------
|
||||
|
||||
|
|
Loading…
Reference in New Issue