Hi all,
We are on Appian 19.1 and in the process of integrating Appian with Blue Prism.
We have used Connected System to call Blue Prism by passing the required parameters.
HostName: https:[machine name]:[port number]
User Id:
Password:
We are getting the below error:
Something went wrong. The following error occurred: class.javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
However, We are able to connect to Blue Prism on "http" and it returns response but not with "https". The error also resembles something related to SSL.
Any pointers would be helpful.
Appreciate an early response!!!
Discussion posts and replies are publicly visible
SSL refers to Secure Sockets Layer, and its what gets you the S in https. Unfortunately, this error by itself leaves little to go on. For some reason, you don't have the connection secured.
From what I've gathered this error occurs when you attempt to use https to try to connect to something that's not using https, when you try to securely connect to something that isn't secured. This would mean the problem is likely from the Blue Prism side. It's either not using https, it's not on a secured port, or something in the configuration of the connected system is acting like it's not secured, causing this error to happen when you try to connect to it via SSH.
I wish I could be of more help, but I only have the error message to go on.
Hi David,
Thanks for your response.
As informed in my post, I was able to connect to BluePrism using "http" but not with "https"
The question is why the endpoint on "https" is not connecting to BluePrism when the credentials and the [hostname:portnumber] are good.
Unfortunately, I dont have anything else to share beyond this error message. I'm not able to see anything in logs either except for the message
Check to see how the Connected System, Appian, and Blue Prism are all configured. If any of them is only http, then it won't be able to communicate. Both ends have to be held to secure standard, or both ends have to accept only plaintext. So if you're having trouble raising one end to secure standard, it's likely because the other end is not secure standard yet. Either that, or something in the middle is making it appear that way.