Solved

ClientId or clientSecret is not provided. Continue without authentication

  • 20 July 2023
  • 1 reply
  • 15 views

Userlevel 7
Badge +2
  • Community Manager
  • 101 replies

I get the following error message:

 

2023-07-18 11:18:01 +2 [INF] Starting ToscaExecutionClient...

2023-07-18 11:18:01 +2 [INF] Parameter "eventsConfigFilePath" defined. Using configuration from file.

Get-Content : Der Pfad "...." kann nicht gefunden

werden, da er nicht vorhanden ist.

In ...\tosca_execution_client.ps1:581 Zeichen:22

+     $script:events = Get-Content -Path $eventsConfigFilePath -Raw

+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : ObjectNotFound: (C:\....) [Get-Content], ItemNotFoundException

    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetContentCommand

 

2023-07-18 11:18:01 +2 [WRN] ClientId or clientSecret is not provided. Continue without authentication...

2023-07-18 11:18:01 +2 [INF] Enqueue execution with provided parameters...

2023-07-18 11:18:01 +2 [ERR] ToscaExecutionClient failed to enqueue the execution.

2023-07-18 11:18:01 +2 [ERR] Der Remoteserver hat einen Fehler zurückgegeben: (401) Nicht autorisiert.

 

I tried the following command lines, none of which specify aeventsConfigFilePath and none of that worked giving slightly different error messages:

 

powershell tosca_execution_client.ps1 -toscaServerUrl %DEX_URL% -projectName %DEX_Project% -events TestEvents -clientId=%Tosca_Client_ID% -clientSecret=%Tosca_Client_Secret%

powershell tosca_execution_client.ps1 -toscaServerUrl %DEX_URL% -projectName %DEX_Project% -events TestEvents clientId=%Tosca_Client_ID% clientSecret=%Tosca_Client_Secret%

powershell tosca_execution_client.ps1 -toscaServerUrl %DEX_URL% -projectName %DEX_Project% -events TestEvents clientId %Tosca_Client_ID% clientSecret %Tosca_Client_Secret%

 

Could you please provide one full working example so I can get a feel for what a correct command line looks like? Thank you.

 

[Originally asked and solved on Support Hub]

icon

Best answer by Kat 20 July 2023, 16:25

View original

1 reply

Userlevel 7
Badge +2

Answering my own Question:

The -events option doesn't work as documented. At least not in the version I was using. Use -eventsConfigFilePath and a JSON file instead. It's cleaner and scales better anyway.

The correct syntax is using a single dash and space(es) between parameter name and parameter value.

powershell ToscaExecutionClient\tosca_execution_client.ps1	^
-toscaServerUrl %DEX_URL% ^
-projectName %DEX_Project% ^
-eventsConfigFilePath %~dp0\%DEX_Job%.json ^
-clientId %DEX_Client_ID% ^
-clientSecret %DEX_Client_Secret% ^
-creator %USERNAME%:%DEX_Job% ^
-importResults true

Reply