App Proxy, write_app_proxy scope and old merchants

Authentication & Access
1

Hi there,

I have a question about the Application Proxy. We’re using it extensively across several apps. I noticed that the new write_app_proxy scope is now required to use the App Proxy, which is totally fine - but what about existing users?

We have many merchants already using our app. We’ve added the new scope, so any merchant who visits the app admin panel will be prompted to accept it. But what happens to merchants who won’t visit the admin panel before November 14 and therefore don’t accept the new scope? Will the App Proxy stop working on their storefronts?

The concern is that most merchants use our admin panel only once to configure the app and then rarely return, even though they rely on the app’s functionality on the storefront. If it suddenly stops working for them without warning, that would create a really bad experience.

Could you please clarify what exactly will happen to existing stores using App Proxy if they haven’t accepted the write_app_proxy scope by November 14?

Thanks!

2

Hey Denis,

Great to hear you’ve already made this change. Digging into this on my side, to get clarification on what will happen once the deadline is reached.

1 Like
3

Thanks, Liam. Please let me know once you have any information.

4

Hi again Denis,

For merchant stores that don’t accept the new scopes, we’ll backfill the scope on our side, so they won’t experience any disruption when using your app. Since you’ve added the scope correctly there’s nothing else you need to action.

2 Likes
5

Great, thanks for the confirmation!

1 Like