REST Token or header in inheritable

Question

question

ozn asked Nov 7, '17 ovidiu_constantin answered Nov 7, '17

REST Token or header in inheritable

When we commonly use REST API to wherever, we need to include some token or cokie in each the REST query. After we create a session profile, we pass the handle in different procedure/quick calls. When we do that in the the REST query step does not inherit the token or header. We are using global variable/parameters to get the values. Is there a better way you guys suggest?

In python, once we modify the rest session object in one place, we don't have to worry about it in each query. This seems to be an issue in itest, at least not very straight forward.

rest rest session profile

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2017-11-07T12:15:53Z

ovidiu_constantin answered Nov 7, '17

Hello @ozn

I'm Ovidiu from Spirent support.

The current implementation of the rest session is set to be inline with the whole iTest functionality.

I'm presuming you're setting the token as a variable in a HTTP header on the open step.

As it is expected, if the variable is local it will not be seen by a subsequent procedure/quickCall.

As you stated, the solution is either to set the token variable as global or set it in a parameter.

The modification to the rest session needs to be done only in one place (at the open step ) and the rest of the steps related to that session will inherit the changes.

Please let me know if this is the behavior you are seeing.

Thank you.

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

question