how to use goth for gitlab when deploying the application on production
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.6k
- Forks
- 631
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I am trying the use `goth` in my production application. The application is configured to use `gitlab` as oauth provider. When I try to run the application locally, it works fine but when I move the same application to production, it gives me the below error
```
oauth2: cannot fetch token: 401 Unauthorized
Response: {"error":"invalid_client","error_description":"Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method."}
```
Any idea?
The redirect uri which is being getting created is as follows `https://oauth.myapplication.com/auth/gitlab/callback`
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
No file, test, or entry point is named. Start by comparing the local and production Goth GitLab OAuth configuration, including client credentials, authentication method, and the shown redirect URI. Done means the production deployment completes the GitLab token exchange without the invalid_client error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100