Use Xcode 15 with 3DS2 v2.3.2

[tontonbibi]

Hello,

Context :
We currently have our project running on Xcode 15. We are still using Adyen SDK v4.X (our backend is not ready yet for 5.X)
So we tried to use Adyen SDK v4.11.0 that contains Xcode 15 fix. But according to the release note, 3DS2 sub-dependancy has been moved to 2.3.3

Our issue is that 3DS2 v2.3.3 now requires to use directoryServerRootCertificates, and our backend is not ready yet.

So we are kind of stuck for now because, for some technical reason we cannot go back to Xcode 14. And our backend will be ready too late (we are supposed to release a new version of the app very soon).

Question :
Is it reasonable to point the commit revision just before the 3DS2 upgrade and just after Xcode 15 fix ? (rev. 916f8e2)
So we keep using 3DS2 v2.3.2 (without mandatory certificate directory) with a working Xcode 15 version

Is there security consideration doing that ? or something else ?

Thank you very much for your help.

Tontonbibi
iOS tech lead

[descorp]

Hey @tontonbibi

Sorry for the inconvenience.
Xcode 15 release was a bit of turmoil moment for many of us 😅

Is it reasonable to point the commit revision just before the 3DS2 upgrade

This is safe to do as a temporary measurement till your backend is ready to utilise directoryServerRootCertificates property.

our backend is not ready yet.

Could you describe your use-case in detail?
How does introduction of directoryServerRootCertificates change your backend setup?
Do you generate your own 3DS Fingerprint Token?

[tontonbibi]

Hi @descorp,

This is safe to do as a temporary measurement till your backend is ready to utilise directoryServerRootCertificates property.

Thanks a lot for your answer ! We will use this specific revision for now.

Could you describe your use-case in detail?
How does introduction of directoryServerRootCertificates change your backend setup?

I am really not an expert on that part sorry, our backend team is a different team from mine.
First I thought this directoryServerRootCertificates could have been hardcoded in our iOS app. But when I asked them for this directoryServerRootCertificates, they said it was dynamic and it could change. So we are stuck until they modify their endpoint and send this field to us.
Were they wrong ?

[descorp]

@tontonbibi

Were they wrong ?

It depends on the use case :)

I asked them for this directoryServerRootCertificates, they said it was dynamic and it could change.

directoryServerRootCertificates is indeed dynamic, but our Checkout API is capable to provide correct certificate stored on Adyen Backend automatically and use it to generate 3DS2 Fingerprint Token.
Unless one's backend is generating own 3DS2 Fingerprint Tokens, there is no extra work needed from one's side to adopt to new 3DS SDK v2.3.3 🤔