E9.2 Parameterized URL

HI plgbpedro2,

To authenticate, you must use the AIS REST API for Token validation/generation before calling the Orchestration.

With the token in your hands, you have to add it to the JSON body of your Orchestration.

So, if your Orchestration has an empty body (no inputs), then you have to add the following:

{
"deviceName": "yourDevName",
"token": "09kjdf0239u#3928uewo23..."
}

This will make the "Authentication for your Orchestration automatically.

In fact, you ALWAYS must use this technique on ALL your Orchestrations. 😉

Um abraco!

- Barizon
 
HI plgbpedro2,

To authenticate, you must use the AIS REST API for Token validation/generation before calling the Orchestration.

With the token in your hands, you have to add it to the JSON body of your Orchestration.

So, if your Orchestration has an empty body (no inputs), then you have to add the following:

{
"deviceName": "yourDevName",
"token": "09kjdf0239u#3928uewo23..."
}

This will make the "Authentication for your Orchestration automatically.

In fact, you ALWAYS must use this technique on ALL your Orchestrations. 😉

Um abraco!

- Barizon
Thank you, Barizon!
 
Hi @plgbpedro2,

you can too login orchestrator with username an password in the each request body:

{
"username": "USER",
"password": "JDEPASS",
(other params)
}

But it's better with tokens as said Gustavo
Best regards.
 
Back
Top