WINRM Rundeck 2.1.2 - Login failure

[George Preston]

This is the error I get trying to control my windows system from Rundeck running on a Linux system:
[overthere-winrm:xxx.xxx.xxx] failed: WinRM Error: Login failure sending message on https://xxx.xxx.xxx:5986/wsman error: unable to find LoginModule class: com.sun.security.auth.module.Krb5LoginModuleRequest: <?xml version="1.0" encoding="UTF-8"?> <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"> <env:Header> <a:To xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">https://xxx.xxx.xxx:5986/wsman</a:To> <a:ReplyTo xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <a:Address mustUnderstand="true">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:Address> </a:ReplyTo> <w:MaxEnvelopeSize xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" mustUnderstand="true">153600</w:MaxEnvelopeSize> <a:MessageID xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">uuid:904C648F-39B9-480F-BDB6-CB206B3F0306</a:MessageID> <w:Locale xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" mustUnderstand="false" xml:lang="en-US"/> <p:DataLocale xmlns:p="http://schemas.microsoft.com/wbem/wsman/1/wsman.xsd" mustUnderstand="false" xml:lang="en-US"/> <w:OperationTimeout xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">PT60.000S</w:OperationTimeout> <a:Action xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" mustUnderstand="true">http://schemas.xmlsoap.org/ws/2004/09/transfer/Create</a:Action> <w:ResourceURI xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" mustUnderstand="true">http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd</w:ResourceURI> <w:OptionSet xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd"> <w:Option Name="WINRS_NOPROFILE">FALSE</w:Option> <w:Option Name="WINRS_CODEPAGE">437</w:Option> </w:OptionSet> </env:Header> <env:Body> <rsp:Shell xmlns:rsp="http://schemas.microsoft.com/wbem/wsman/1/windows/shell"> <rsp:InputStreams>stdin</rsp:InputStreams> <rsp:OutputStreams>stdout stderr</rsp:OutputStreams> </rsp:Shell> </env:Body> </env:Envelope> Response: [EMPTY]

Can anyone provide some help?
Thanks

[Vince H]

Looks like you're using Kerberos authentication (which is default). Are you encountering the same issue with basic?

[Leandro Skully]

I'm facing the same issue. I tried changing to basic authentication, but the error is as follows:

[overthere-winrm:xxxxxx.xxxxxx.xxxx] failed: WinRM Error: Unexpected HTTP response on http://xxxxxx.xxxxxx.xxxx:5985/wsman:   (401)

20:55:32 Failed: WinRMProtocolError: WinRM Error: Unexpected HTTP response on http://xxxxxx.xxxxxx.xxxx:5985/wsman:   (401)

20:55:32 HOSTNAME Execution failed: 37: [Workflow result: , step failures: {1=Dispatch failed on 1 nodes: [YYYYYYYYY: WinRMProtocolError: WinRM Error: Unexpected HTTP response on http://xxxxxx.xxxxxx.xxxx:5985/wsman:   (401)]}, Node failures: {YYYYYYY=[WinRMProtocolError: WinRM Error: Unexpected HTTP response on http://xxxxxx.xxxxxx.xxxx:5985/wsman:   (401)]}, flow control: Continue, status: failed]

[Leandro Skully]

An update on this issu, if I execute winrm manually, using either Kerberos or No authentication (none). I can execute it normally. I can't execute it with basic auth without "Access denied".

I've configured the krb5.ini.

I've set permissions correctly on winrm (Basic, Kerberos, AllowUnencrypted and Trusted hosts - all true and *).

Verified network issues with Server Manager and both machines can execute PS and list each one Services, resources, etc.

I'm completely stuck. If someone can help me I'll appreciate. 

I'm using Rundeck 2.5.1 + WinRM plugin 1.3.1

On Thursday, June 12, 2014 at 3:32:54 PM UTC-3, Vince H wrote:

[APWAM BY]

Hi Leandro, 

Did you get this problem resolved?

I'm having problem run WinRM (on remote Win Server).

Thanks.

[edu...@rundeck.com]

Hi APWAM,

What type of issue do you have with running WinRM? Which plugin  are you using? winrm plugin or py-winrm plugin? any error log you may have and some details about your setup/configuration, such as authentication method, etc, are useful as well.

Cheers!