ResourcePC commands + internal auth

FelixGerdwilker — Thu, 30 Mar 2023 17:26:48 GMT

Hello community,

I am trying to use the http ResourcePC commands in conjunction with the internalauth parameter. I am not really getting it to work and both the documentation and the existing thread help me solving this. So maybe someone has an idea whats wrong here or even can tell if this should not work.

I am creating an auth token using AutomateC:

.\AutomateC.exe /getauthtoken /user $bpuser $bpuserpw /dbconname $connectionname

From my understanding this should post as an interanalauth Token.

When I try to add this to my http-request:

http://{{Server}}/createas+{{TOKEN FROM shell: aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeee_iiiiiiii-jjjj-kkkk-xxxx-yyyyyyyyyy}}+{{ProcessId}}

From my observation this consists of the user ID and some token: {{TOKEN FROM shell aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeee_iiiiiiii-jjjj-kkkk-xxxx-yyyyyyyyyy}} and represents almost the same as if you use getAuthToken <ProcId> <User> <password> - from the documentation I take the the token from AutomateC should be a general token while the latter one only is applicable to a single process.

I am glad if someone may know how to solve this or if I am on the wrong track.

One addition: In the long run I may even want to user createas+name as the process names feel more static than the ids.

Thanks and best regards

Felix

Re: ResourcePC commands + internal auth

hossein.azimi — Sun, 23 Apr 2023 22:52:14 GMT

Hello Felix

I suggest reviewing the following knowledge base for this question:

How to use the Runtime Resource HTTP commands to run a Process

Best regards

topic Re: ResourcePC commands + internal auth in Product Forum

ResourcePC commands + internal auth

Re: ResourcePC commands + internal auth