Greetings.
=================================
Background (prior to asking the questions)
In regards to: Netlify API documentation
We are considering the scenario when a Netlify OAuth2 app will require many different possible redirect_uri
endpoints. Many distributed app servers could host the implementation.
=================================
Questions
Question 1: When acquiring a token, is the redirect_uri
parameterizable or flexible in any way? Can we add multiple redirect_uri
endpoints, use globs for pattern matching, or maybe dynamically define the redirect_uri
at authorization time? (The latter, or all, might introduce security risks. Asking to confirm, nonetheless.)
Question 2: If the redirect_uri
is locked to a single URI then one thought is to create a single endpoint that will proxy the call using the state
value. Is this a viable option?
Question 3: In the UI it appears that we can define a Netlify OAuth2 App. (I don’t see this option in the swagger file.) Meaning, we can create/set the Application Name and Redirect URI via the API. Is this a valid scenario? Or, would this scenario require authorization prior to this action can be done programmatically?
=================================
Thank you for your time!