Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
9 replies
Subscribers
7 subscribers
Views
5006 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
# a!httpQuery Is there any way to pass a specific TLS version say 1.2, in t
manojj
over 7 years ago
# a!httpQuery
Is there any way to pass a specific TLS version say 1.2, in the http request using the httpQuery function or any other way?
OriginalPostID-215060
OriginalPostID-215060
Discussion posts and replies are publicly visible
0
chetany
A Score Level 1
over 7 years ago
If you want to specify the TLS version, I think you can specify it in header. Since you are using httpQuery, I would suggest using a!httpHeader in it to specify the TLV version in the header. I think the header will also depend on the server you are querying (if it is Apache or JBOSS etc..) This is just my suggestion, I might be wrong..
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
chetany
A Score Level 1
over 7 years ago
typo correction "TLS" instead if TLV
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
manojj
over 7 years ago
thanks chetany for the quick response, so to be specific, I need to understand the syntax for the same, what will be the values for name/value pair in : a!httpHeader( name, value)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
chetany
A Score Level 1
over 7 years ago
You can try a!httpHeader("tls-version", "TLSv1.2"). Please note that this may not be the correct answer. The name of the header may depend on the webservice/server of URL that you are calling
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
chase.putnam
over 7 years ago
None of this is correct.
TLS versions are configured on each Web Server and the SSL handshake commences prior to any HTTP traffic being exchanged. The highest available TLS/SSL version available on each web server is selected to encrypt the HTTP traffic and then the HTTP traffic is exchanged.
Look at your web server configurations and ensure you have TLS v1.2 enabled. Then you can look to ensure that any web services you are connecting to also support TLS v1.2.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
manojj
over 7 years ago
That explains it, thanks a lot Chase for the detailed reply, so if TLS v1.2 is not enabled there is no way I can set it through request or header parameters.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
manojj
over 7 years ago
that raises one more query in my mind, so if I enable TLS 1.2, the requests to API which only supports TLS 1.1 or 1.0 will also be covered? Please pardon my naïve queries as I have not come across TLS version conflicts in past.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
chase.putnam
over 7 years ago
That is correct as headers are a part of the HTTP traffic and not a part of the SSL handshake that takes place before any HTTP traffic is initiated.
The SSL handshake will try and use the highest TLS/SSL version available on both servers.
You must enable each other version of TLS you wish to also use as otherwise any services that implement a lower TLS version will not be able to connect with you as they will not see you supporting lower versions.
You can contact any web service administrators for services you may be implementing to ask if they can enable TLS v1.2 as I would think any security recommendations and updates are always a welcome request from customers/end users. Then they may be able to implement this and get your service calls to use TLS v1.2.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
manojj
over 7 years ago
thanks a ton Chase, cheers!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel