Using username and password as authentication method is deprecated, instead the access token should be used now.

We have to extend configuration options to enter the access token, and if provided to use that.

In order to prevent using this old approach, we should hide the old config options from admin UI for new config entities, as well as for editing the ones already using the bearer. For the existing ones with the old authentication scheme, we should of course allow to change the values, but also add a message that this is deprecated now, and the access token should be used instead

Comments

agoradesign created an issue. See original summary.

agoradesign’s picture

crediting jrochate for informing about this change

jrochate’s picture

Thanks.

I got information from SIBS (Portugal) that username/passwd schema will work until end of June.

After that all auth will be token only.

New installations / services are now being only supplied with token.

The token can be managed via platform backoffice, as state here:

https://sibs.docs.onlinepayments.pt/reference/parameters#authentication

agoradesign’s picture

thanks for the information!

agoradesign’s picture

I've written an e-mail to Viveum, asking how they treat this in Austria

  • agoradesign committed 4f31a06 on 8.x-1.x
    Issue #3134495 by agoradesign, jrochate: Allow to use access token (...
agoradesign’s picture

Please note that the commit in #7 is just preparation work, doing the necessary refactoring work in order to get the request initialization on a single place

  • agoradesign committed cb4b41c on 8.x-1.x
    Issue #3134495 by agoradesign, jrochate: Allow to use access token (...

  • agoradesign committed 85943d0 on 8.x-1.x
    Issue #3134495 by agoradesign, jrochate: Allow to use access token (...
agoradesign’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.