search

openbankingspace / tpp-issues

34 stars 1 forks source link

Barclays - Unable to complete mobile third party authorisation journey #159

Open maria-robobug opened 5 years ago

maria-robobug commented 5 years ago

NOTE: We are using the legacy endpoint (https://oauth.tiaa.barclays.com/as/authorization.oauth2) with the authondevice=YES parameter

[Error OBA14] - When attempting to give third party permission from the Barclays mobile app, an error is returned after submitting the access code provided on the https://openbanking.barclays.co.uk page. This occurs after selecting "Give your permission" and entering the six digit code presented on the web page.

Expected

User should be able to successfully consent to third party permissions and be redirected to said third party.

Actual

'[Error OBA14] Something went wrong...' message is returned on the mobile app and the user in unable to proceed.

Impact

An unknown proportion of users are unable complete the consent journey an thus access Open Banking services. This appears to be intermittent but is affecting us in the majority of cases.

ghost commented 5 years ago

For anyone who is still struggling with this issue like my company had been for the past 2 weeks, even after copying requests from other TPPs, what causes the errors to appear on the mobile app has to do with the OAuth Profile settings for the app. If your TPP app has been registered through the developer portal, you should be able to disable OpenID Connect Supported option in the OAuth Profile section of the settings. That seems to have fixed all issues we were having with client authentication through the mobile app.