Hi Matteo,

Trust you've seen the documentation for ExecuteHttpRequest and that you are familiar with the HTTP protocol. And to add some context, hoping you are familiar with cURL, think of ExecuteHttpRequest as a light-weight version of cURL build into TI but limited to HTTP.

With that in mind the question of having to specify an authentication header, or the '-u' username:password for basic authentication shortcut, with your HTTP request which you are preforming using ExecuteHttpRequest depends on the service you are targeting. In this case the target is a PA 3.1 service (not TM1 directly) in which case the answer is not only 'Yes' you'll need to follow a device-code-flow with your OIDC provider, the one you used to configure PAL 3.1, and then pass the resulting token in the 'Authorization' header as in: `Authorization: Bearer <token>`. Truth be told though, not sure if this pattern is already documented in the preliminary PAL 3.1 docs.

But all that said I notice you are talking about Windows Integrated Security. Not that it is impossible to use Windows Integrated Security with PAL 3.1, or TM1 v12 for that matter, but neither have support for Windows Integrated Authentication build in any longer, so how did you set that up? What OIDC provider are you using to bridge between the two?

curl -X PUT  "<DataBricks URL>/api/2.0/fs/files/Volumes/<My DataBricks Target Directory>/dropbox/<My File Name>.csv" -H "Authorization: Bearer <My Databricks Token>"   -H "Content-Type: application/octet-stream"  --data-binary @/Users/<my Local ID>/Downloads/My Local File Name>.csv  

Hi Matteo,

Trust you've seen the documentation for ExecuteHttpRequest and that you are familiar with the HTTP protocol. And to add some context, hoping you are familiar with cURL, think of ExecuteHttpRequest as a light-weight version of cURL build into TI but limited to HTTP.

With that in mind the question of having to specify an authentication header, or the '-u' username:password for basic authentication shortcut, with your HTTP request which you are preforming using ExecuteHttpRequest depends on the service you are targeting. In this case the target is a PA 3.1 service (not TM1 directly) in which case the answer is not only 'Yes' you'll need to follow a device-code-flow with your OIDC provider, the one you used to configure PAL 3.1, and then pass the resulting token in the 'Authorization' header as in: `Authorization: Bearer <token>`. Truth be told though, not sure if this pattern is already documented in the preliminary PAL 3.1 docs.

But all that said I notice you are talking about Windows Integrated Security. Not that it is impossible to use Windows Integrated Security with PAL 3.1, or TM1 v12 for that matter, but neither have support for Windows Integrated Authentication build in any longer, so how did you set that up? What OIDC provider are you using to bridge between the two?

Hi Matteo,

If it's HTTP then there shouldn't be anything that CURL can do that ExecuteHttpRequest can't (that I'm aware of). Your example above should work just fine as in:

```
ExecuteHttpRequest(
'PUT',
'<DataBricks URL>/api/2.0/fs/files/Volumes/<My DataBricks Target Directory>/dropbox/<My File Name>.csv',
'-h Authorization: Bearer <My Databricks Token>',
'-h Content-Type: application/octet-stream',
'-d @/Users/<my Local ID>/Downloads/My Local File Name>.csv' );

```

curl -X PUT  "<DataBricks URL>/api/2.0/fs/files/Volumes/<My DataBricks Target Directory>/dropbox/<My File Name>.csv" -H "Authorization: Bearer <My Databricks Token>"   -H "Content-Type: application/octet-stream"  --data-binary @/Users/<my Local ID>/Downloads/My Local File Name>.csv  

Hi Matteo,

Trust you've seen the documentation for ExecuteHttpRequest and that you are familiar with the HTTP protocol. And to add some context, hoping you are familiar with cURL, think of ExecuteHttpRequest as a light-weight version of cURL build into TI but limited to HTTP.

With that in mind the question of having to specify an authentication header, or the '-u' username:password for basic authentication shortcut, with your HTTP request which you are preforming using ExecuteHttpRequest depends on the service you are targeting. In this case the target is a PA 3.1 service (not TM1 directly) in which case the answer is not only 'Yes' you'll need to follow a device-code-flow with your OIDC provider, the one you used to configure PAL 3.1, and then pass the resulting token in the 'Authorization' header as in: `Authorization: Bearer <token>`. Truth be told though, not sure if this pattern is already documented in the preliminary PAL 3.1 docs.

But all that said I notice you are talking about Windows Integrated Security. Not that it is impossible to use Windows Integrated Security with PAL 3.1, or TM1 v12 for that matter, but neither have support for Windows Integrated Authentication build in any longer, so how did you set that up? What OIDC provider are you using to bridge between the two?

curl -X PUT  "<DataBricks URL>/api/2.0/fs/files/Volumes/<My DataBricks Target Directory>/dropbox/<My File Name>.csv" -H "Authorization: Bearer <My Databricks Token>"   -H "Content-Type: application/octet-stream"  --data-binary @/Users/<my Local ID>/Downloads/My Local File Name>.csv  

Hi Matteo,

Trust you've seen the documentation for ExecuteHttpRequest and that you are familiar with the HTTP protocol. And to add some context, hoping you are familiar with cURL, think of ExecuteHttpRequest as a light-weight version of cURL build into TI but limited to HTTP.

With that in mind the question of having to specify an authentication header, or the '-u' username:password for basic authentication shortcut, with your HTTP request which you are preforming using ExecuteHttpRequest depends on the service you are targeting. In this case the target is a PA 3.1 service (not TM1 directly) in which case the answer is not only 'Yes' you'll need to follow a device-code-flow with your OIDC provider, the one you used to configure PAL 3.1, and then pass the resulting token in the 'Authorization' header as in: `Authorization: Bearer <token>`. Truth be told though, not sure if this pattern is already documented in the preliminary PAL 3.1 docs.

But all that said I notice you are talking about Windows Integrated Security. Not that it is impossible to use Windows Integrated Security with PAL 3.1, or TM1 v12 for that matter, but neither have support for Windows Integrated Authentication build in any longer, so how did you set that up? What OIDC provider are you using to bridge between the two?

curl -X PUT  "<DataBricks URL>/api/2.0/fs/files/Volumes/<My DataBricks Target Directory>/dropbox/<My File Name>.csv" -H "Authorization: Bearer <My Databricks Token>"   -H "Content-Type: application/octet-stream"  --data-binary @/Users/<my Local ID>/Downloads/My Local File Name>.csv