Question
UNIQA
PL
Last activity: 23 Jun 2021 13:54 EDT
Pega Studio - Pega Robot Manager: connection with server failed
Hi guys,
while building the connection between Pega Robotic Studio and Pega Platform an error occurs: Server rejected credentials. You are no longer authenticated.
What we have done:
1. Pega Robotic Studio is installed on VM. We checked acces to the Pega Platform directly from this machine. It works
2. Pega Studio: Tools > Options > Pega Robot > Server Connectivity (as described here: https://academy.pega.com/topic/deploying-robot-manager/v1):
- Server - RobotManager, PegaDevServer - we checked both,
- adress filled, proxy - filled and empty (both checked),
3. authentication details - the same as used in step nr 1. Checked for two different accounts
4. Test Connection > error: Server rejected credentials. You are no longer authenticated.
In some other post there was suggestion to uncheck security in API (please see screen below). We have also done this with the same result.
Do you have other hint what can block this connection? Are there other, specific options in Pega Studio / Robot Manager / Platform that we should check?
Versions used:
- Pega Robot Studio: 19.1.76.0
-
Pega Platform 8.5.3
Thanks a lot for your help.
Pegasystems Inc.
GB
Hi,
From version 8.5 we don't depend on the standard Platform API. We do use robotics Service Package only.
Could you check the security in that Service Package?
Thanks
Updated: 18 Jun 2021 2:14 EDT
UNIQA
PL
combinations checked:
1) API Service Package - authentication unchecked + robotics Service Package authentication unchecked (screen attached)
2) API Service Package - authentication checked + robotics Service Package authentication unchecked
both with the same result: Server rejected credentials. You are no longer authenticated.
Pegasystems Inc.
GB
Could you trace the request and share the screenshot?
UNIQA
PL
how can I try to trace this connection between Studio and Robot Manager? Should we use specific tool? If so, what would you recommend?
Pegasystems Inc.
GB
In the robotics Service Package, locate and open the latest Data endpoint. Open it on the top right of the rule form you have an option to trace the service.
Then try to test the connection from Robot Studio to get the case details. This should be traced if you are calling that RM instance.
Updated: 21 Jun 2021 9:38 EDT
UNIQA
PL
Please find below the steps we executed in the system:
1. We turned on Service monitoring on the level of robotics Service Package
2. From the Pega Robot Studio, we tested the connection to Pega Robot Manager - we tried with multiple ways of defining the address: plain http (with the Requires authentication checkbox unselected in the Sevice Package form), https, ip address alone, ip address + port etc.
3. We checked the Invocation History of every service method in the robotics Service Package, but we didn't find a trace of any historical execution.
To trace an execution, we need to know which service method is called with the click of the button Test Connection in the Pega Robot Studio. Could you, please, check it for us, so we can do this exercise on our end? However, as I mentioned, we checked the invocation history of each of the service methods available there, so I am not sure if tracing any of the methods may give us more information.
What is more, just to check if the connection between Pega Robot Studio and Pega Robot Manager is possible to establish, we called from Pega Robot Studio's automation randomly picked service method (from api Service package) and it worked fine. In attachment please find the screens.
Pegasystems Inc.
GB
Looks like you're not connecting to that RM instance and the issue is in the connection. You can try to copy and paste the URL used in the config in a web browser to confirm that the URL it is correct.
If the URL is correct perhaps there is a firewall or a web proxy configured that you need to configure or a Load Balancer that is not properly configured.
I've seen web proxies causing similar issues on multiple clients.
Could you check this?
UNIQA
PL
Ok, we will check, but if the problem is with the connection, shouldn't we have the same situation (lack of response) in case of calling Pega's api from the automation created in Robot Studio?
As I mentioned in my previous post, we did it successfully and also we could ping the VM with Pega Platform from machine with Robot Studio. I believe that in case of firewall proxy problem, we would not do this.
Any other sugestions? Maybe we could have some screensharing session to go through this process? If necessary, I can create SR in MSP.
Pegasystems Inc.
GB
Yes, please. An INC and having a screen sharing session might be better to asses your particular issue.
Pegasystems Inc.
US
@AngelikaB -
If you open an INC, please reference this post so the Engineer can reference it and let us know the ID and we can monitor for you as well!
Thanks!
Pegasystems Inc.
GB
@MarissaRogers INC-180038 has been logged and we will look into it.
Pegasystems Inc.
US
Thanks @Marije_GCS!