Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
tutorial:adm:configuration_-_winrm [2019/10/08 13:28]
fiserp [Commons issues] 		tutorial:adm:configuration_-_winrm [2019/10/08 13:38]
fiserp [Commons issues]
Line 119: Line 119:
  
  
-==== Commons issues ====+==== Common issues ====
 === Specified credentials were rejected by the server === === Specified credentials were rejected by the server ===
 Can be caused by: Can be caused by:
Line 149: Line 149:
 </code> </code>
 This seems to be caused by older versions of the ''cryptography'' python library. Upgrading the library should solve the problem. Since this library is also used by some OS components, we recommend to upgrade it locally only for the user who runs python winrm scripts. This seems to be caused by older versions of the ''cryptography'' python library. Upgrading the library should solve the problem. Since this library is also used by some OS components, we recommend to upgrade it locally only for the user who runs python winrm scripts.
 +
 +=== Requests using non-urllib3 backend ===
 +<note important>Please note this is **not** a fix to your situation. For more info, look at [[https://github.com/requests/requests-kerberos/issues/128|this Github issue]].</note>
 +This affects only ''requests-ntlm'' library and therefore only NTLM authentication. It does not seem to affect the overall function but the warning is at least an annoyance. When you see the warning:
 +<code>
 +/usr/lib/python2.7/site-packages/requests_ntlm/requests_ntlm.py:200: NoCertificateRetrievedWarning: Requests is running with a non urllib3 backend, cannot retrieve server certificate for CBT
 +  NoCertificateRetrievedWarning)
 +</code>
 +You can confirm the behavior by:
 +  - Installing ''requests-ntlm'' locally for the user.
 +  - Editing ''~/.local/lib/python2.7/site-packages/requests\_ntlm/requests\_ntlm.py'' and changing the import ''from requests.packages.urllib3.response import HTTPResponse'' to ''from requests.packages.urllib3 import HTTPResponse''.
 +  - When running winrm script with NTLM, the warning should no longer pop up.
 ===== HTTPS support ===== ===== HTTPS support =====
 The best case is to use HTTPS connection to connect to WinRM. To achieve this we need to do some more configuration on the server and on the client. The best case is to use HTTPS connection to connect to WinRM. To achieve this we need to do some more configuration on the server and on the client.
  • by erbenr