core:\content\Applications\PowerShell
.OnLoad
.core:\content\Applications\Content Editor\Context Menues\Default\
.Spe.IdentityServer.config
\App_Config\Include\Spe.config
.RemoteAutomation.asmx
.RemoteScriptCall.ashx
.RemoteScriptCall.ashx
.RemoteScriptCall.ashx
.RemoteScriptCall.ashx
.RemoteScriptCall.ashx
.RemoteScriptCall.ashx
.RemoteScriptCall.ashx
.requireSecureConnection
, you may find that this causes a 403 status code when testing against a server hosted behind a load balancer. If the load balancer maintains the TLS certificate and forwards traffic to a backend web server over port 80 .Net will not recognize this as a secure connection.Spe.config
. There is a generic list of permissions configured by default but we highly encourage you to adjust to meet your security requirements.<authorization/>
section is removed and custom roles are then added.<deny>
element as described here in sitecore modules\PowerShell\Services\web.config
.sitecore modules\PowerShell\Services\
you'll need to use the Credential parameter for any command that interacts with the services. See the Remoting section for examples.App_Config\Include\Spe\Spe.config
App_Config\Include\Spe\Spe.Minimal.config
bin\Spe.dll
bin\Spe.Abstractions.dll
sitecore modules\PowerShell\Services\web.config
sitecore modules\PowerShell\Services\RemoteAutomation.asmx
sitecore modules\PowerShell\Services\RemoteScriptCall.ashx