I'm working on an old project using Savon to connect to the SalesForce api. I'm getting this error:
UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization. Please use TLS 1.1 or higher when connecting to Salesforce using https
How do I get it to use TLS 1.2? Or is there a simple alternative to Savon that does use TLS 1.2?
Savon uses HTTPI as a common interface for Ruby's HTTP libraries
Configure Savon to use a specific library with:
HTTPI.adapter = :httpclient
HTTPI.adapter = :curb
...
it currently tries the libs in the following order:
[:httpclient, :curb, :em_http, :excon, :net_http, :net_http_persistent]
If you haven't installed httpclient, it will try curbnext and so on.
You should try setting an explicit lib and see if it works for you.
Just to help others in the future who may face the same problem. It seems the TLS level is not built in the savon gem but in the httpi adapter. By changing the adapter to httpclient (installed the gem, put require 'httpclient') the savon gem starts using it without further configuration. Just remove the ssl_level params and the latest and more modern cypher is used. Problem solved.
Related
Does Mailkit SMTP support TLS 1.3?
This is a short and sweet question, but in my googling for an answer I couldn't find a definitive response. Further I couldn't find a simple test email server, or service, where I could lock down the protocols such that only TLS1.3 was supported so I could do a simple test. And I had to add this paragraph because SO didn't think my one line question was of sufficient quality.
No, MailKit does not support TLSv1.3... but only because the .NET class libraries do not support TLSv1.3.
Once .NET supports TLSv1.3, so will MailKit.
To control which versions of the SSL and/or TLS protocol versions that you want a MailKit client to use, you can set the SslProtocols property to any of System.Security.Authentication.SslProtocols values available for your version of .NET.
Note: It seems that .NET 4.8 will support TLSv1.3
I'm currently creating a chat using elixir. but anytime i try running the app, the websocket gives an error on sever console
The client's requested channel transport version "2.0.0" does not match server's version requirements of "~> 1.0"
And browser console:
WebSocket connection to 'ws://localhost:4000/socket/websocket token=eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJVc2VyOjMiLCJleHAiOjE1MDQ0OTE1NTQsImlhdCI6MTUwMTg5OTU1NCwiaXNzIjoiU2xpbmciLCJqdGkiOiIyNWY5NDZkNy1jNDg5LTRiYWMtYjJkNS0zZDA4OTdkNDU1ZWMiLCJuYmYiOjE1MDE4OTk1NTMsInBlbSI6e30sInN1YiI6IlVzZXI6MyIsInR5cCI6ImFjY2VzcyJ9.nh-DaQfY8OuI0EBE7lILFx6hjm6J_ZrynXHeOLr1-wM-fXnDakqrZUSN1XFQnr0x0KM9WFOkLEQnip5DcsKxXw&vsn=2.0.0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
your phoenix javascript library (dependency) is updated without notice. You should fix version so it is limited to less than 1.3.0 in package.json (if you are using npm) or bower.json if you are using bower to use old implementation, or use narrowtux solution if you downloaded js file manually. Or upgrade phoenix version.
With Phoenix 1.3, a new version of the transport protocol was released. It seems that you've somehow included the new version of the javascript client in your project, but are still running on Phoenix 1.2.
As a workaround, you can copy and reference the old client script here: https://github.com/phoenixframework/phoenix/blob/v1.2/web/static/js/phoenix.js
I have a REST API that was working with Jersey 2.6 and Swagger 1.3.7. I read that Jersey 2.9 fixes a warning that I was getting so I upgraded to the latest Jersey 2.16 but then Swagger stopped working. I went back and upgraded one version at a time until I saw that Swagger was working with 2.15 so I settled on that. Now, the PUT API fails with Swagger with the following error:
The server refused this request because the request entity is in a format not supported by the requested resource for the requested method
The API works using FireFox RESTClient and specifying "application/json".
I do have "jersey-media-json-jackson" as a dependency and call "Client client = ClientBuilder.newClient().register(JacksonFeature.class);" in the program.
I tried upgrading Swagger but that did not help.
Has Swagger been verified to work with Jersey 2.15/2.16?
I've recently managed to get swagger-core to work with Jersey 2.16 with a similar issue. Keep in mind they are using the latest version (1.5.X) and not 1.3.X but the same solution will apply.
The problem is most likely with version resolution, specifically, the one of jackson-databind. For some reason, even jersey-media-json-jackson 2.16 depends on an older version of jackson-databind, even though it works fine with the latest version. Without having more details, it would be difficult to suggest a full solution, but you can follow the dependency tree and see the conflicts there.
If you do require further assistance, I'd suggest either using our mailing list, or even better, the IRC channel where we could interact online and resolve it.
I install Bugzilla on my fedora server. I want to use Rest Api, but can't find how to activate it. Can someone help me?
This issue can be fixed by installing some Perl modules that were listed as optional. What worked for me was enabling mod_rewrite and also installing optional modules pertaining to the Bugzilla API. Make sure that all of the modules you have installed are up to date. You will also want to make sure you enable mod_rewrite so that you can contact /rest/ in your URL instead of /rest.cgi/
Example of enabling mod_rewrite for Windows:
https://tomelliott.com/php/mod_rewrite-windows-apache-url-rewriting
List of modules (required and optional):
https://www.bugzilla.org/releases/5.0/release-notes.html
Take a close look at the table for optional modules. Under the "Enables Feature" function, you will see these two perl modules are required for the API to function.
JSON::RPC (Any) JSON-RPC Interface, REST Interface
Test::Taint 1.06 JSON-RPC Interface, XML-RPC Interface, REST Interface
Note that you may need to look at different pages if you're on a different OS, or want to upgrade a different version.
The REST API is not bundled with the official Bugzilla release. You can get installation instructions here.
I am using Atlassian JIRA™ (Professional Edition, Version: 3.0.3-#75 and Netbeans IDE 7.1
But when trying to validate a connection to Jira from netbeans it gave me this error "Jira RPC services are not enabled"
while I have enabled it and also I enabled allow remote calls in Jira
To be more specific "RPC JIRA Plugin" that I have installed is
The standard JIRA RPC services, both SOAP and XML-RPC.
Plugin Version: 1.1
JIRA version: 3.0
It has
System XML-RPC Services (xmlrpc)
The standard JIRA XML-RPC services.
RPC Field Coordinator (rpcFieldCoordinator)
Issue Service (issueService)
User Service (userService)
Token Manager (tokenManager)
System SOAP Services (soap)
The standard JIRA SOAP services.
Magic Field Validator (magicFieldValidator)
Project Service (projectService)
My global configurations are:
Allow users to vote on issues ON
Allow users to watch issues ON
Allow unassigned issues ON
Cache issues ON
External user management OFF
Logout Confirmation Never
Use Gzip Compression OFF
Accept remote API calls ON
BTW, it is not just netbeans, I got same problem with other tools as well to connect to jira
I will apreciate if my answer be found ASAP .
Thanks
Answering an old question, but I thought someone else might find this useful.
I got the same error today setting up an issue tracker in NetBeans 7.2 and I eventually tracked it down to NetBeans not being able to correctly resolve (using DNS) the (local) host name that was running our JIRA server. When I changed NetBeans to use 'No Proxy' in the main settings, it worked fine.
EDIT: Note that as of version 7.0 of the JIRA server, Atlassian have depracated the SOAP/XML-RPC API, so the JIRA Plugin for Netbeans no longer works. :-(