Drop the use of Salesforce and Google oauth env variables
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
In order to use Salesforce and Google oauth credentials, historically this was facilitated by env variables where the application was deployed with client id and secrets for each provider.
This has been replaced by "Global OAuth Clients", where these client id and secrets (along with all the other OAuth endpoint details) are set via a form and stored in the db.
We should remove the ENV variables, and any references to the config in the application so we can avoid future confusion.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by searching the repository for the Salesforce and Google OAuth environment variables and their application configuration references. Remove the obsolete references and verify that OAuth credentials continue to come from Global OAuth Clients stored in the database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- authentication, backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100