Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By agoradesign on
Change record status:
Published (View all published change records)
Project:
Introduced in branch:
8.x-1.x
Introduced in version:
8.x-1.0-rc11
Issue links:
Description:
Beginning in rc11, we are dropping support for the deprecated user ID and password authentication in favour of the access token approach, as user ID + password will soon no longer be accepted in API calls. The exact deadline depends on your Open Payment Platform provider. In Portugal, SIBS will drop support in June 2020, in Austria Viveum in September, for example.
Please note, that you shouldn't update to rc11, unless you know your correct access token! User ID and password are no longer used.
Update hook 8109 automatically calculates and sets the access token based on the previously configured user ID and password, but it's strongly advised to check the correctness of the calculated access token!
The access token is basically nothing but a base 64 encoded concatenation of user ID and password, glued together with a '|' pipe character, but configuration overrides in your current environment can lead to a false value. It's quite common to have live settings in Drupal configuration and define overrides with test environment credentials in local dev and staging environments (or vice versa).
Impacts:
Site builders, administrators, editors
