May 7, 2016

Authentication Security Enhanced

We have improved security for the authentication process.

CAPTCHA is no longer shown to you after you tried to log in to the GoodData platform and repeatedly provided wrong credentials. Instead, you are allowed to make another attempt to log in after a certain period of time.

How does this affect you?
If you use a tool for handling API calls, you may need to update how it processes the server response to a failed login attempt due to wrong credentials.

  • Old behavior: The server returned a status code of 401, 'Unauthorized'.
  • New behavior: The server returns a status code of 401, 'Unauthorized' to a failed login attempt. After a certain number of invalid login requests, the server returns a status code of 429, ‘Too many requests’. The response contains the ‘Retry-After’ HTTP header. This header specifies the period (in seconds) after which you can attempt to log in again. The number of seconds between attempts increases with each successive failed login.

Learn more:
Authentication via API
API: Login Use-case
API: Log in

 

SSH Host Keys Changed

We have updated the SSH host keys for our SFTP service. The new fingerprints are as follows:

44:f2:67:d5:a4:ab:bd:30:07:2d:6f:ab:21:85:70:4e secure-di.gooddata.com (RSA)
b9:90:bf:8f:0f:c9:e1:82:64:c0:f8:59:78:f8:87:f6 secure-di.gooddata.com (DSA)
b2:fe:aa:70:d0:7c:6b:51:46:bc:72:b1:fa:3d:c1:3b  na1-di.gooddata.com (RSA)
66:0d:61:22:2b:b7:14:68:70:d8:be:29:db:2d:dd:76 na1-di.gooddata.com (DSA)

How does this affect you?
If needed, update the processes uploading your data to the GoodData platform.

 

Data Distribution Platform (DDP) Renamed to Automated Data Distribution (ADD)

We have renamed Data Distribution Platform (DDP) to Automated Data Distribution (ADD). The Portal user interface and documentation have been updated accordingly.

Learn more:
Automated Data Distribution

 

API: Upcoming Change of Maximum Number of Elements

For API call responses, we are planning to change the maximum number of returned elements that can be displayed on a page.

When you use API to get all the elements belonging to a certain attribute (for example, you want to see all the individual cities belonging to the city attribute), the API call returns these elements as a list. If the list contains too many elements, it is broken down into pages, through which you can navigate.

Currently, the maximum number of the elements that can be displayed on a page is 600.000. We are going to set it to 10.000 to prevent performance issues.

How will this affect you?
If you use a tool for handling API calls where the number of the returned elements is set to 0 or to a value greater than 10.000, this value will be ignored, and the maximum of 10.000 elements per page will be returned. If the number of the returned elements is not set, it will default to 10.000.

We will post a separate announcement when this change happens. Stay tuned!

Have more questions? Submit a request

Comments

Powered by Zendesk