Welcome! We're glad you're here.
In the Ideas Portal, we encourage you to share your ideas and feature improvements for RingCentral products. Whether you're an admin supporting your whole team on the RingCentral app, an employee attending meetings with RingCentral Video, or a developer using integrations, we want to hear from you!
You're invited to browse existing ideas, vote on features you would like to see, and leave comments sharing your use case.
We've put together a helpful guide for getting the most out of Submitting and Voting for Product Ideas.
We can't wait to hear your bright ideas!
When testing our app, sometimes we'll use a redirect URI that appends a canary branch. For example, if we have the redirect URI https://ourservice we may have a test branch URI of https://ourservice/branch/bugfix-1 or https://ourservice/branch/bugfix-2. Instead of having to go into the console and specify each redirect URI, it'd be nice to have a wildcard, for instance https://ourservice/branch/*.
We recognize the utility of this feature, however, IETF specifically recommends against this approach
For example OAuth 2.1 (still in draft says (https://datatracker.ietf.org/doc/html/draft-ietf-oauth-v2-1-04#section-2.3.2):
And https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics-18#section-2.1
I really like the idea, btw.
I'd add a branch name variable, site location/IP identifier within your code as a tag to automatically load the proper console. (If name=Houston, then load /houston-branch/*.)
Good idea. What if this change happened within your code by adding a drop down to choose between the wildcards?