gitea: Drone auth not working with internal users
- Gitea version (or commit ref): 1.8.1
- Git version: N/A
- Operating system: Linux
- Database (use
[x]):- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
- Log gist:
Description
Drone no longer works with Gitea as of 1.8.1. Logging into drone is successful in so much as I see it creates an access token in Gitea even after I delete it. After drone logs in and creates the token, it then hits /api/v1/user. Gitea responds with 401 Unauthorized.
I switched back to 1.8.0 as a workaround for now. Sorry I do not have more details. The logs were not very detailed. I suspect some of the auth bug fixes in 1.8.1 could have caused this. Can anyone else confirm drone no longer working with Gitea?
Screenshots
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 9
- Comments: 27 (12 by maintainers)
It worked earlier for me but I have just had a recurrence. I had to go into Gitea -> Settings -> Applications and delete the ‘drone’ token, after which Drone could then reconnect (recreating the token). I’m not yet sure what the cause is.
Update: And it just happened again after logging out of Drone - deleting the token then fixed it, so something is not right somewhere. The token-create API call does return a different sha1 each time, suggesting that it is recreating the token as it should be.
Running both gitea and drone on latest docker images (managed by containrrr/watchtower - which is the newly maintained v2tec/watchtower).
settings -> applications -> Manage OAuth2 applicationsRedirect URImust be identical to that used from drone. Mine is https://<url-to-drone>:<port-of-drone>/loginYou need to set the env parameters in the docker container
DRONE_GITEA_CLIENT_IDandDRONE_GITEA_CLIENT_SECRET- both generated in step 1./2. after saving.What I need to adjust was
DRONE_SERVER_HOSTwhich seems to have the port also - otherwise the redirect uri is not constructed proper.That’s it…
@lunny don’t you think it would be more beneficial to put it into the drone docs as that’s the system that wants to authenticate? I could check if they would accept a pull request on their docs for an addition in oauth2 with gitea.
Can confirm having the same problem with gitea version
1.9.0+dev-223-g6db3dc7c0and and latest drone. Was working fine until gitea update.@kimpenhaus that’s better.
Let me add some additional information here. Looks like I have the same issue with the following setup:
Docker compose:
nginx configuration:
After loggin in on drone.<server> i get the message “Login Failed. Unauthorized”.
docker compose log: