I am running VRO 7.3 with HTTPS-REST Plug-in 2.2.2. Apparently this issue was/is fixed in the latest VRO.
This is what the release note says:
The REST API client does not encode and decode space characters correctly.
- When querying scripting actions by their fully qualified names with the REST API client, the space characters are incorrecly encoded as
%2B
or a plus (+
) character. As a result, the request fails with anScript module not found
error message.
But I am still having this issue.
I have two workflows.
1. Authenticating the user so that I get a token to make my REST API calls
2. Using my token to perform other API calls like search for a IP address.
Here is the log that contains my current issue from the 2nd workflow:
This is what the original token looks like:
Here is the javascript. I am pretty sure that the attribute fullUrl is encoding my token to that "%253D%253D" which obviously invalidates the token.
-The only workaround I've found was to hardcode it to the restOperation template, but that defeats the purpose since tokens expire.
Do you guys happen to have a workaround or something?
Any help will be greatly appreciated!