Best practice for oAuth apps with scopes which not all customers have

We are working with customers that may not have all the features (e.g. DSS) that our app uses. However, those features are optional. Currently, the OAuth workflow will prevent customers from authorizing the app if they don’t have all the scopes that we request.

Is there a better way to address this scenario besides creating 2 apps with differing scopes?

Hey @zoomdev ,

Great question, right now, the best approach is to make two OAuth apps with different scopes.

We will have conditional scopes at some point in the future.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.