-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
404 After Logging into Decap #7172
Comments
+1, seeing exactly the same behavior. The request to GitLab 404s. When I make the same exact request (using cURL) and change the Authorization header by replacing "token" with "Bearer," the request succeeds. |
+2 can confirm - same issue with a self-hosted gitlab instance. |
Does login work on your setups with any of the previous versions of Decap? |
@martinjagodic I hardcoded the version to 3.1.2, and I logged in without issue. So it seems there was a regression. |
@peterstory 3.1.2 is the version you mentioned in the original comment as the one with the problem. The latest is 3.1.10. If you have some time, could you check which versions have the problem and which don't? So we can identify the culprit more easily. |
To clarify, when I opened the issue my admin page used this URL: Then, I edited the URL to be: So I have the error with 3.1.10, and I don't have the error with 3.1.2. |
I'm having the same problem using "the latest version", when reverting to specific 3.1.2 the problem no longer exists. Using gitlab.com |
Was being driven mad by this issue today. I found the exact piece of code that is causing the issue.... At the following link you can see a piece of code was introduced that calls getDefaultBranchName() decap-cms@3.1.2...main#diff-c2b33fd12ce38e1438c9c43cd2be709d291d165dd6a70dd8c4377d3a075fdad1 getDefaultBranchName() calls apiRequest() apiRequest() calls constructRequestHeaders() constructRequestHeaders() then explicitly uses "token" instead of "Bearer" (which is what gitlab requires) causing the error to be thrown |
…Bearer" (decaporg#7242) The authorization type "Bearer" is more widely recognized than "token". E.g. Gitlab requires that you use "Bearer". This should fix decaporg#7172 where apparently login with Github was broken by this line: decaporg#7172 (comment) See also: decaporg#5844 (comment)
…Bearer" (#7242) The authorization type "Bearer" is more widely recognized than "token". E.g. Gitlab requires that you use "Bearer". This should fix #7172 where apparently login with Github was broken by this line: #7172 (comment) See also: #5844 (comment)
Describe the bug
After logging into Decap, I get a "404 Project Not Found" error.
To Reproduce
Expected behavior
The Decap CMS GUI should load.
Screenshots
I'm stuck at "Logging in..."
Applicable Versions:
CMS configuration
https://trinityworc.gitlab.io/admin/config.yml
Additional context
Console errors:
This request was successful:
This request gave a 404:
The text was updated successfully, but these errors were encountered: