brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [1/2] brooklyn-docs git commit: Clarifications on using Invoke-Command
Date Wed, 30 Mar 2016 09:18:52 GMT
Repository: brooklyn-docs
Updated Branches:
  refs/heads/master 137e7565b -> ad52f8dfa

Clarifications on using Invoke-Command


Branch: refs/heads/master
Commit: 687c07ee8050ccd9c4d730af35540173e70ae76b
Parents: 137e756
Author: Valentin Aitken <>
Authored: Tue Mar 29 22:33:47 2016 +0300
Committer: Valentin Aitken <>
Committed: Tue Mar 29 23:02:54 2016 +0300

 guide/yaml/winrm/ | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/guide/yaml/winrm/ b/guide/yaml/winrm/
index f20b72b..56a66a3 100644
--- a/guide/yaml/winrm/
+++ b/guide/yaml/winrm/
@@ -296,8 +296,10 @@ For this reason you should enable CredSSP on the windows host which grants
all p
 To use `Invoke-Command -Authentication CredSSP` the Windows Machine has to have:
-- Up and running WinRM over http. Notice that we support winrm over https but for Invoke-Command
to work it needs up and running winrm over http.
-  Apache Brooklyn can winrm over https but if the install script has inside it `Invoke-Command
-Authentication CredSSP` then winrm over http has to be enabled as well.
+- Up and running WinRM over http. The custom-enable-credssp.ps1 script enables winrm over
http because `Invoke-Command` use winrm over http by default.
+  Invoke-Command can be used with -UseSSL option but this will lead to modifying powershell
+  With always enabling winrm over http on the host, blueprint's powershell scripts remain
consistent and not depend on the winrm https/http environments.
+  We hope future versions of winrm4j will support CredSSP out of the box and wrapping commands
in Invoke-Command will not be needed.
 - Added trusted host entries which will use Invoke-Command
 - Allowed CredSSP

View raw message