I installed a self-hosted standalone setup of Repman yesterday (manual install running on Ubuntu 22.04 / PHP 8.1 / Nginx) and got everything working perfectly, with OAuth authentication against a self-hosted GitLab installation working for both logins and also adding/syncing packages. All of this worked absolutely fine with GitLab v16.10-ee.
However upon updating GitLab to v16.11-ee the OAuth flow no longer works, returning a 500 error with the message "An error occurred while refreshing the access token: Bad Request".
I've tried regenerating my OAUTH_GITLAB_CLIENT_ID and OAUTH_GITLAB_CLIENT_SECRET's, removed and recreated an organization within Repman etc. but nothing appears to resolve the issue.
Hi there,
I installed a self-hosted standalone setup of Repman yesterday (manual install running on Ubuntu 22.04 / PHP 8.1 / Nginx) and got everything working perfectly, with OAuth authentication against a self-hosted GitLab installation working for both logins and also adding/syncing packages. All of this worked absolutely fine with GitLab v16.10-ee.
However upon updating GitLab to v16.11-ee the OAuth flow no longer works, returning a 500 error with the message "An error occurred while refreshing the access token: Bad Request".
I've tried regenerating my OAUTH_GITLAB_CLIENT_ID and OAUTH_GITLAB_CLIENT_SECRET's, removed and recreated an organization within Repman etc. but nothing appears to resolve the issue.
Any assistance would be greatly appreciated!
Many thanks Lee