# Idea OP-7971 - OAuth applications for dev/test purposes

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-7971

## RICE

| Attribute | Value |
| --- | --- |
| Reach |  |
| RICE Score |  |
| Votes |  |

## Requires

_No work packages_

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |

## Details

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Target versions | Wish List |
| Module |  |
| Priority | Medium |
| List |  |
| Interest by |  |
| Labels |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |

## Description

Hello\! 

I will talk about this page  \<base-open-project-url\>/admin/oauth/applications

When you develop something, that needs this OAuth connection, you have to do some additional work, which is not part of you primary work. I mean open the doc site, create OAuth app, select correct options, copy-paste client ID and secrets into the code, find collegues who can help you with this if you don't well know oauth protocol and so on. Even after this you can't ask another collegues to work with you, because if they create their container they can't use your credentials. Thay should repeat those operations again. The same if you try to continue work from another computer.

This is fine for production but in dev process this work unnecessary waste time. For my point of view for dev purposes the other workflow seems the best. Maybe you find it well too.

For dev process i would prefere fixed predefined OAuth application into newaly created OpenProject container. This OAuth application can be setted throough the docker's ENV or it may be special dev-container into DockerHub predefined OAuth application and documented credentiaals. That is my suggestion.

Thanks\!
