cancel
Showing results for 
Search instead for 
Did you mean: 

Exposing a Web Service Authentication

KirstenA
Level 3
Hello,

We use Blue Prism 5.0.30.

We would like to switch to exposing an Object as a Web Service for data ingestion to create queue items.

I am able to set up the object in a local instance of Blue Prism and successfully transfer data using Basic Authentication to send my own credentials with the SOAP API call.

When I move to my development / test environment, which uses Active Directory for user authentication, I cannot complete authentication for SOAP - I do not know what parameters to send.  I am struggling to find documentation on authentication - I'm not even sure if I'm asking the right questions.

Is authentication possible in this scenario?

Thank-you,


------------------------------
Kirsten Avarmaa
Business Systems Specialist
Empire Life
America/Toronto
------------------------------
1 BEST ANSWER

Helpful Answers

The final answer is that we were using a version of Blue Prism with a bug for SOAP in it.

------------------------------
Kirsten Avarmaa
Business Systems Specialist
Empire Life
America/Toronto
------------------------------

View answer in original post

8 REPLIES 8

Hi, Kirsten,

it should work the same way as without SSO. Did you try to send your username and password in your SOAP API call? I have a client where they've got SSO at Blue Prism level and SOAP calls work fine with provided username/password.

Regards,

------------------------------
Zdeněk Kabátek
Head of Professional Services
NEOOPS
http://www.neoops.com/
Europe/Prague
------------------------------

In my local instance, I have a 'user account' set up with admin privileges.

When I use basic authentication to send the request, authentication is able to complete.

In my development environment, I don't have a name or password for Blue prism.  When I pass my network credentials in the SOAP request, I receive an authentication error.  I cannot add a user in Security > Users and assign a name or password.

------------------------------
Kirsten Avarmaa
Business Systems Specialist
Empire Life
America/Toronto
------------------------------

Hi, Kirsten,

it is not about having a user in Blue Prism. In SSO authentication it is done through Microsoft Active Directory so you cannot add it as you described. It is correct. However, you still can access Blue Prism because your windows account is part of MS AD group which is assigned certain permission within BP environment.

So if you use your domain account in your SOAP call with your password that should work fine. Do you use SOAP UI tool? You choose there only Basic Authentication and add username and password (your windows account) and it should work fine.

Regards,

------------------------------
Zdeněk Kabátek
Head of Professional Services
NEOOPS
http://www.neoops.com/
Europe/Prague
------------------------------

Hello Zdeněk,

We are using both SOAPUI (5.5.0) and Postman as part of our validation tools.  We have been able to successfully GET (without authentication), but not perform POST methods.

In SOAPUI we get the response HTTP/1.1 401 Unauthorized

In postman I can use basic or inherited auth which results in (editted): the same 401 unauthorized error.

Thank-you for your feedback.  It is reassuring to know we're on the right track!

------------------------------
Kirsten Avarmaa
Business Systems Specialist
Empire Life
America/Toronto
------------------------------

Hi, Kirsten,

I am attaching the screen shot from SOAP UI. You can see in the bottom part the basic authentication where I used my BP account and password. That is on my local machine but the same approach works for SSO. You just need to specify your windows account and password.

Regards,
15121.png


------------------------------
Zdeněk Kabátek
Head of Professional Services
NEOOPS
http://www.neoops.com/
Europe/Prague
------------------------------

Hello Zdeněk,

I appreciate the screenshot  I have been able to use the authentication box in order to connect to my local instance of Blue Prism, but not our SSO dev region.  Thank-you for confirming that we are on the right path.


------------------------------
Kirsten Avarmaa
Business Systems Specialist
Empire Life
America/Toronto
------------------------------

I believe we may have found our error - we were trying to validate first with http, instead of https, but an MS AD server requires a secure connection.

------------------------------
Kirsten Avarmaa
Business Systems Specialist
Empire Life
America/Toronto
------------------------------

The final answer is that we were using a version of Blue Prism with a bug for SOAP in it.

------------------------------
Kirsten Avarmaa
Business Systems Specialist
Empire Life
America/Toronto
------------------------------