Release notes for the 7.x-1.x versions

mydigipass 7.x-1.7

Release date: February 4, 2017

Added functionality that allows the automatic creation of a Drupal account when a new MYDIGIPASS.COM user connects to the site. In the previous version, when a MYDIGIPASS.COM user connected to a Drupal site for the first time, then the user was asked whether he already had an account on the Drupal site or whether he wanted to create a new one. With this update, it is possible to configure the module so that a new Drupal account is created automatically for the user. This improves the user experience since a user is not bothered with user registration questions on a website where they want to log on with their MYDIGIPASS.COM account.

mydigipass 7.x-1.6

Release date: January 28, 2017

Removed validation of input that was too strict: when communicating with MYDIGIPASS.COM, the modules receives an authorization code and access token from MYDIGIPASS.COM. The previous versions included a check to verify that the authorization code and the access token had the correct format. It checked on the type of characters and on the length of the code or token. A change has been made to MYDIGIPASS.COM which caused that the implemented validation was too strict which caused that valid authorization codes and access tokens were found to be incorrect. Therefore, the validation has been removed from the module.

Only check for API inconsistency if the integration was enabled: MYDIGIPASS.COM requires that a site administrator performs user accounting: it has to be checked whether the correct number of users that use MYDIGIPASS.COM have been reported to MYDIGIPASS.COM. The module checks for inconsistencies between the number of users maintained by the website and the number of users maintained by MYDIGIPASS.COM. In previous versions, this check was always performed when the MYDIGIPASS module was enabled. However, it could then happen that the module was not yet configured (for example the client_id was not yet configured) when this check is done, but this causes that the API calls to MYDIGIPASS.COM fail. As of the current version, the check is only done when the module is enabled and when the integration with MYDIGIPASS.COM is effectively enabled.

Changes to work with different user data scopes: the module now supports data-scope attribute which determines which attributes should be requested about a certain user (see https://developer.mydigipass.com/reference_guide_button#data_scope_values).

mydigipass 7.x-1.5

Release date: July 22, 2015

Changes to the MYDIGIPASS.COM button interface caused that the module no longer functioned properly when using the module with a self-registered developer website. This release fixes this and allows developers to use the Drupal module again.

This release also fixes a bug in the code where Drupal's database API function rowCount() was used to SELECT-queries. rowCount() should however not be used on SELECT-queries, but only on INSERT, UPDATE and DELETE-queries. The effect was that the rowCount() always returned 1 when using a database other than MySQL. All occurrences where rowCount() was used have been updated with countQuery() queries.

This release does not contain any database schema changes.

mydigipass 7.x-1.4

Release date: November 27, 2014

MYDIGIPASS.COM has changed its policy so that e-mail addresses will only be present in the list of shared attributes if the user has confirmed his e-mail address. See: https://developer.mydigipass.com/news#_only_confirmed_e_mail_addresses_can_be_shared
Since the releases previous to this version assumed that the e-mail attribute was always present, it was used in some cases. The changes in this release mainly check for the presence of the e-mail attribute before using it.
Not updating to this release may result in PHP notices about "Undefined index" in Drupal's watchdog.

Other changes:

  • In some cases, the message in the "Status report" contained a hyperlink pointing to a no longer existing module page.
  • When adding the MYDIGIPASS.COM button to a form, the class attributes are now passed in an array.

There are no database schema changes.

mydigipass 7.x-1.3

Release date: November 17, 2013

  • Implementation of the MYDIGIPASS.COM logout feature: when enabled, a popup is displayed after logout to users who logged in with MYDIGIPASS.COM to ask them if they also want to log out of MYDIGIPASS.COM.
  • Updated the link to the dp_connect.js file.
  • Implemented the multi-language feature of MYDIGIPASS.COM so that button-helptext can be displayed in the user's native language.
  • Moved the connectivity test button to the advanced settings form.
  • Changed all test-urls (used in the connectivity test and the ssl certificate test) to the data_origin url.
  • Implementation of 3 API functions to allow Drupal developers or other modules to interact with the MYDIGIPASS.COM module:
    • mydigipass_logged_in_with_mydigipass(): Allows to check whether the current user is logged in with MYDIGIPASS.COM.
    • mydigipass_user_data_by_drupal_uid(): Returns the MYDIGIPASS.COM user data for a certain Drupal UID.
    • mydigipass_user_data_by_mydigipass_uuid(): Returns the MYDIGIPASS.COM user data for a certain MYDIGIPASS.COM UUID.

mydigipass 7.x-1.2

Release date: November 3, 2013
  • Updated the hardcoded location from where the MyDIGIPASS.COM dp_connect.js file is loaded.
  • Moved the security settings admin page to the advanced settings admin page.
  • Provided an interface that allows site administrators to change all MyDIGIPASS.COM endpoint and API URLs.

mydigipass 7.x-1.1

Release date: September 1, 2013
  • Implementation of the MYDIGIPASS.COM (dis)connected endpoints: the module now notifies MYDIGIPASS.COM of (dis)connected users.

mydigipass 7.x-1.0

Release date: February 17, 2013
  • First release of mydigipass module for Drupal 7.
  • Supports all features of the Drupal 6 module.
  • Also supports strict SSL certificate validation to prevent man-in-the-middle attacks between the webserver and mydigipass.com.