cancel
Showing results for 
Search instead for 
Did you mean: 

Blue prism SOAP Authentication error

Rama_krishna
Level 4

Hi All,

When we are configuring to blue prism RT machines getting SOAP Authentication error in windows 2019 server. Please help me to resolve error.

1 BEST ANSWER

Helpful Answers

expertcr
Staff
Staff

We documented how to resolve that in the following KB Article (LINK HERE). That issue happened after an update from Microsoft and is required to set the SPN on the Blue Prism server.

View answer in original post

7 REPLIES 7

Asilarow
MVP

Could you give more context on this error please? When does it show up exactly? 
Can you provide a screenshot?

Andrzej Silarow

Hi @Asilarow 

Thanks...,

please find below screen shot. Below error we are getting, connecting RT machine to app server

Rama_krishna_0-1715308820146.png

 

This means that your server is using the SOAP protocol for authentication, and your SOAP authentication headers sent from the resource machine are not valid.

You should configure your resource machine connection settings to match those on the server:

Asilarow_0-1715333390023.png

You can find more details on this topic here

Andrzej Silarow

Rama_krishna
Level 4

we are able to connect app server.

We configured as per the document but we are getting soap error in RT machines.

 

I think this issue lies in the server set up, the server will be running but the callback protocol will likely be the issue preventing the application from connecting to it. If log into the application server and you go to the folder BP is installed in and open the BPServer e.g. C:\Program Files\Blue Prism Limited\BPServer.exe

When this opens select edit and then select the ASCR Settings tab and in here you will need to change the callback protocal to gRPC and in the Binding settings under Hostname you need to add your server name.

michaeloneil_1-1715765221567.png

 

 

Hi @michaeloneil 

Thanks..,

we don't have ACSR setting Tab

we are using blue prism 6.10.1 version.

expertcr
Staff
Staff

We documented how to resolve that in the following KB Article (LINK HERE). That issue happened after an update from Microsoft and is required to set the SPN on the Blue Prism server.