<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=23054) </details> <!--IssueSummary end--> Due to security concerns, it wouldn't be safe to allow wildcards for OAuth application redirects. Instead, we propose to add API endpoints to manage OAuth applications. This will allow automated systems to add/update OAuth applications with the appropriate redirect URI on the fly. ## Original description ### Problem to solve Gitlab OAuth provider can only have fixed `redirect uri` parameters. ### Further details I'm using gitlab as a OAuth provider for my app, but I can't redirect a user to the page they are coming from. I can only redirect them to a static site which I have to set as the redirect uri in my created application. ### Proposal Add wildcards to `redirect_uri` somewhere around here https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/initializers/doorkeeper.rb#L105 ### What does success look like, and how can we measure that? Can users set wildcards in redirect uris and do they work. ### Links / references https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/initializers/doorkeeper.rb#L105