topic Resource PC Commands in Product Forum

Resource PC Commands

l.kiciak — Thu, 04 Jun 2020 08:21:00 GMT

Hi,

I'm trying to figure out how to use resource commands.
If I'm getting it right the first step is to authenticate myself. According to help:

http://localhost:8181/user%20admin&password%20MyPassword

But I constantly receive authentication failed. I tried with my user or robo users and outcome is the same. Can it be, it's because of using SSO? Additionally the credentials are working passed through SOAP request.

The next thing is /getauthtoken command.
I'm able to generate a token through automatec.exe, but I didn't found any place, where it can be used. I checked the Web Service Guide and there is only basic authentication mentioned for accessing exposed processes/objects.

Did any of you are using those commands and could give me some advice how to handle them?
A documentation or example of using /getauthtoken, would more than appreciated.

Many thanks for any bit of advice,
Best,
L

RE: Resource PC Commands

John__Carter — Thu, 04 Jun 2020 10:04:00 GMT

This has tripped me up too. Try http://localhost:8181/user%20name%20admin&password%20MyPassword and then bang your head on the desk.

------------------------------
John Carter
Professional Services
Blue Prism
------------------------------

RE: Resource PC Commands

John__Carter — Thu, 04 Jun 2020 10:07:00 GMT

And look at the internalauth command for using tokens

------------------------------
John Carter
Professional Services
Blue Prism
------------------------------

RE: Resource PC Commands

l.kiciak — Thu, 04 Jun 2020 13:44:00 GMT

Hi John,

you are right, the issue was missing 'name' word in the string.
http://localhost:8181/user%20name%20admin&password%20MyPassword
http://localhost:8181/user%20userID&password%20MyPassword

Currently I'm facing another issue, when I try to create a session using:
http://localhost:8181/create%20name%20ProcessName
http://localhost:8181/create%20ProcessID
Following error appears:
ERROR : Value can not be null, or have zero length
Parametername: TokenValue
The process is published if it makes a difference.

Command:
http://localhost:8181/createas%20Token%20ProcessID
works.

Best,
L

------------------------------
Łukasz Kiciak
RPA Developer
UI
Europe/London
------------------------------

RE: Resource PC Commands

John__Carter — Fri, 05 Jun 2020 08:01:00 GMT

Hi Lukasz, the use of the command line changed recently so that by default user permissions are enforced. When this setting is enabled, Create no longer works and you must use CreateAs instead. Likewise StartAs and DeleteAs. https://bpdocs.blueprism.com/bp-6-8/en-us/sysman-settings.html

------------------------------
John Carter
Professional Services
Blue Prism
------------------------------

RE: Resource PC Commands

l.kiciak — Fri, 05 Jun 2020 11:56:00 GMT

Hi John,
thanks for clarification!

I have had some other issues, but was able to solve them 🙂

Best,
L

RE: Resource PC Commands

MayankGoyal2 — Sun, 28 Jun 2020 21:21:00 GMT

@John Carter - Hi John, kindly suggest if environment is on SSO, http://machinename:8181/user%20name%20admin&password%20MyPassword, what value should I provide for user name and password in that case. I have a central machine from which I want to check the status of a resource PC on different machines on environment with - http://machinename:8181/user%20name%20admin&password%20MyPassword&status.

------------------------------
Mayank Goyal
------------------------------

RE: Resource PC Commands

bruce.liu — Mon, 29 Jun 2020 04:56:00 GMT

Hi Mayank,

Username can be either one of the following:

samaccountname (where it will look for the user in the domain specified in Blue Prism)
DOMAIN\samaccountname
userprincipalname i.e. something@some.domain

Password is what is associated with the AD account. I have tested all three in my environment and they all worked.

------------------------------
Bruce Liu
Senior Product Consultant, Professional Services
Blue Prism
Australia/Sydney
------------------------------

RE: Resource PC Commands

MayankGoyal2 — Tue, 30 Jun 2020 03:45:00 GMT

@Bruce Liu - Thanks a lot for your response. It worked great and we were able to get a response in SSO environment. Just a quick confirmation for my understanding, when environment is not on SSO and I have a different username and password for machine login and BP login, in that case we will have to mark Blue prism login credentials in http url as it has nothing to do with machine login credentials?

------------------------------
Mayank Goyal
------------------------------

RE: Resource PC Commands

bruce.liu — Tue, 30 Jun 2020 03:51:00 GMT

Hi Mayank,

Yes, you were right on this.

Essentially you are attempting to log onto a Blue Prism runtime resource (RR). For a non-SSO environment, you must supply native Blue Prism credentials, something the administrator must configure in the System -> Security -> Users section beforehand. Machine login credentials are needed to start up the RR, this is needed before you can issue the HTTP request with Blue Prism credentials set in the process.

------------------------------
Bruce Liu
Senior Product Consultant, Professional Services
Blue Prism
Australia/Sydney
------------------------------