- Drill to another KPI Dashboard
- Data loading switched to the new IP addresses
- Old GoodData public PGP key expired
- GoodData Ruby SDK 2.1.10 available!
- REMINDER: Use TLS Version 1.2 or higher only
In KPI Dashboards, you can now configure drilling to another KPI dashboard in your workspace.
When you click a measure, the target KPI dashboard then opens in the same window.
You can configure drilling for each measure included in an insight on the dashboard.
Drill to Another KPI Dashboard
As we announced earlier, we switched to using the new IP addresses that are used for loading data to your GoodData projects. The deprecated IP addresses are no longer in use.
If you have not whitelisted the new IP addresses and you rely on IP whitelisting, the new IP addresses may be blocked on the side of your data sources. As a result, new data is not fetched from your data sources and is not loaded to your GoodData projects.
Here is how you can fix this:
- Find out what datacenter holds your data.
- Check this article, and make sure that the IP addresses listed for your datacenter are whitelisted and allowed on the level of your data source.
- (Optional) Delete the deprecated IP addresses from your whitelist.
For customers using the GoodData PGP SSO login implementation
As we announced earlier, the old GoodData public PGP key that you used to encrypt your PGP login requests expired.
If you have not updated the key on your side, you now cannot log in to the GoodData platform via SSO. To fix this, download the new public PGP key and update the key on your side.
You can also download the new PGP key from our online help here (go to Step 3) or here (go to Step 3).
NOTE: To review the old key, see this article.
We have released version 2.1.10 of GoodData Ruby SDK.
This version brings improved performance in operations related to managing users in domains and projects.
We recommend that you update to the latest version of the Ruby gem or get the source code from our GitHub repository.
Support for Transport Layer Security (TLS) version 1.0 and 1.1 is deprecated and will end on August 13, 2020.
How will this affect you?
All modern web browsers and programming languages already support the newer versions of TLS (1.2 and higher). Unless you use obsolete software or unsupported systems, you are not affected.
You may be affected if you are using an older version of the libraries or programming languages in your tools. To verify, check the documentation for your tool:
- Java: https://blogs.oracle.com/java-platform-group/jdk-8-will-use-tls-12-as-default
- Microsoft Windows: https://docs.microsoft.com/en-us/security/solving-tls1-problem
- Python: https://docs.python.org/3/library/ssl.html
- Ruby: https://blog.rubygems.org/2018/02/24/tls-10-and-11-deprecation-notice.html
Before August 13, 2020, make sure that all your components and integrations use TLS version 1.2 or higher.
What will happen if you do not upgrade to the newer versions?
Support for TLS version 1.0 and 1.1 will end on August 13, 2020. After that date, if you do not switch to a newer version of TLS, the integration with the GoodData platform will stop working.