How to Fix the SSLProtocolException: handshake alert

-
You might have probably encountered the following error when invoking a web service over HTTPs transport using SoapRequestReply activity.

 "javax.net.ssl.SSLProtocolException: handshake alert:  unrecognized_name"

This could be a weird error especially if you know that the client certificates are valid, and you have installed the complete certificate chain in your keystore. In order to resolve this, you need to add the following property in the application .TRA file.

java.property.jsse.enableSNIExtension=false

I don't have an exact explanation for the root cause of this error, but I believe this is brought about by one of the the security enhancements in Java SE 7.

"Server Name Indication (SNI) for JSSE client: The Java SE 7 release supports the Server Name Indication (SNI) extension in the JSSE client. SNI is described in RFC4366. This enables TLS clients to connect to virtual servers."

Comments

  1. UnknownMay 25, 2016 at 3:24 AM

    Hi Thanks so much, this piece of info helped me with an issue I've been struggling with

    ReplyDelete
  2. MS DynamicsOctober 2, 2019 at 3:39 AM

    The information which you have provided in this blog is really useful to everyone. Thanks for sharing.
    TIBCO BWCE training in hyderabad

    ReplyDelete

Post a Comment

Popular posts from this blog

XML Schema and JSON Schema Validation in Mule 4

-
Image
Exposing an API to be consumed by client applications entails a lot of challenges. Apart from a good API definition and documentation, you also need to ensure that the request payload submitted to your API endpoints are valid and conforms to the expected data structure. Although it is not required, I think some of the advantages to validate a request payload are: Establish a service contract which is a form of agreement between the service provider and the service consumer. This means that, in order to successfully consume an API, a client application needs to strictly follow a specification "for the request payload" called a data schema . Establish data integrity which ensures that all incoming data submitted to the API are "in a format that is expected". It doesn't make sense to process malformed data. For instance, if you are inserting data to a relational database, it would be more beneficial to first check mandatory (or required) fields before processing th
Read more

Parsing a JSON String and Converting it to XML in TIBCO

-
Image
If you have the REST & JSON Plug-in for TIBCO BusinessWorks, parsing and rendering a JSON string into XML is a straightforward task. We are often using XML in TIBCO, because XML is the most common format that is used to transform data using XSLT and XPath language. There are two ways we can parse and render JSON text: using an XML Schema, and using Java classes. Of course, XML Schema is already very handy, as we can always easily create one in TIBCO Designer. But, before we go to why we need to use Java classes, we need to examine first the nature of an XML Schema. An XSD describes the XML document in a strictly structured manner, which means that the sequence and nesting of the elements are important. However, for JSON, we cannot rely on the order of the elements, and we cannot force JSON to be that way. It’s just its character, and it maintains itself as an unordered collection of zero or more name/value pairs. That said, we cannot expect a JSON message to conform to the sp
Read more

Using XML To Java in TIBCO BW

-
Image
There are cases when it is preferable to use Java code instead of XSLT when doing a complex string manipulation. For example, you would like to produce a single string from the different segments of an XML. You can do this by using XML To Java activity in TIBCO. Suppose you have the following XML: <?xml version = "1.0" encoding = "UTF-8"?> <Employees xmlns = "http://xmlns.tibco.com/javaschema/javaschema.Employees"> <Employee> <Age>24</Age> <Level>2</Level> <Name>Mark Cruz</Name> <Role>Technology Consultant</Role> <Skill>Java</Skill> <Skill>TIBCO</Skill> <Skill>Ruby</Skill> </Employee> <Employee> <Age>25</Age> <Level>1</Level> <Name>John Cruz</Name> <Role>Technology Consultant</Role> <Skill>TIBCO BW</Skill> <Skill>PHP</Skill>
Read more