18-06-26 11:54 AM
We exposed a Blue Prism process as an API, which is being consumed by another team. We had created an Active Directory (AD) user for authentication, allowing them to access the exposed API and load items directly into the Blue Prism queue.
This setup was working as expected in version 7.1.1. However, after the upgrade to version 7.5.1, they are encountering a 401 Unauthorized error while consuming the API.
Could you please assist us in identifying and resolving this issue?
18-06-26 10:00 PM
check for any firewall issues , we also faced same issue , after setting up the firewall we started working fine.
whatever source system is from where you are trying to call exposed process API that should have firewall fix.
23-06-26 09:03 AM - edited 23-06-26 09:03 AM
@naveed_raza We've already checked, there was no firewall issue as it was working fine for previous BP version 7.1.1
23-06-26 02:25 PM
okay, then next check for username , username should be [email protected] whatever your company domain is .. earlier we use to pass only username , now we have to pass username with domain
4 hours ago
@naveed_raza - Apologies for the delayed response. I would like to clarify a few points. We received an AD username from another team and configured it in Blue Prism under Security → Users → AD User. To locate and map the user, we used the Active Directory Name (UPN) format ([email protected]), as the user could not be identified without the domain portion. In Blue Prism 7.1.1, when the exposed API was consumed, a session entry was successfully created in Session Management using the [email protected] account. However, after upgrading to version 7.5.1, the same setup results in an HTTP 401 – Unauthorized Address error.