Ryan Saul April 24, 2013 • Q&A / General Q&A
We here at Jama Support value customer service above everything else. Our goal is to solve your problems and answer your questions as best we can. We strive to answer every question as quickly as possible through our ticket system or on our forums. If your problem needs attention immediately, don't hesitate to call! Please see our numbers and business hours for your area on the right.
Kristina King December 31, 2014 • Q&A / General Q&A
In order to streamline the triaging of tickets as they come in, the Support team is adding a new field to the ticket form, "Severity." A Support engineer will select this value once he or she has assessed the situation given the information in the ticket. When we ask ourselves, "What is the severity of this issue?", we will look to the following definitions:
|1||Jama is down or significantly reduced in a production environment|
|2||Impaired functionality of a major feature or function in a production environment|
Problems with Jama running in a non-production environment, functional/general use questions and non-business impacting problems in a production environment.
NOTE: This is the default Severity if one is not selected by the customer.
Kristina King November 13, 2014 • 3 • Q&A / General Q&A
I just upgraded to 2014.2. Why isn't SOAP API working?
Kristina King October 20, 2014 • Technical Guides / Maintenance
Jama Software takes the security of its customers seriously. As a result, Jama has taken steps to protect against a new SSL vulnerability code named POODLE (Padding Oracle On Downgraded Legacy Encryption). Support has been disabled for SSL V3 on all servers. Testing shows that this should not affect existing customers, since all browsers supported by our application can use the newer TLS encryption standards.
What makes this vulnerability unique is that it allows attackers to force connections with secure websites to use a vulnerable version of SSL, which could allow attackers to see encrypted data. This vulnerability affects only SSL V3, which is an older encryption standard that has been around since 1996 and was superseded by TLS 1.0 in 1999. Most servers and applications still support SSL V3 for backward compatibility with older applications.
Jama’s systems will continue to support newer versions of TLS 1.0, 1.1, and 1.2. While we do not believe any customers will be affected by this change, we recommend that API customers verify use of a version of JRE 1.4 or higher that supports TLS. Customers using our SOAP API should also verify that their libraries have TLS support. Finally, anyone using IE 6 or older should upgrade to a newer browser.
If you have any questions or concerns about our response to this vulnerability, please open a support ticket.