mirror of
https://github.com/RayLabsHQ/gitea-mirror.git
synced 2026-04-25 15:25:55 +03:00
[GH-ISSUE #29] [Feature Request] OIDC / Forward Auth #15
Labels
No labels
bug
documentation
enhancement
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/gitea-mirror#15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CrazyWolf13 on GitHub (Jun 23, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/29
Hi
It would be awesome to have OIDC or Forward auth, examples:
https://docs.goauthentik.io/docs/add-secure-apps/providers/proxy/header_authentication
https://docs.goauthentik.io/integrations/services/bookstack/
That would be awesome, because one could simply log into main auth provider and not have to log in again on each selfhosted app.
Therefore log in automatically into gitea-mirror.
I guess it's best to decide, if the app stays single-user then header auth may probably be the best, if multi-user OIDC/Oauth.
@arunavo4 commented on GitHub (Jun 24, 2025):
I have been debating about single and multiple user casue I feel if people have multiple github accounts they could make seperate user accounts and have it work that way. but single account is just easier to manage. Will think more on it and see what I decide on
@CrazyWolf13 commented on GitHub (Jun 24, 2025):
Yeah, I'd currently think single user is better for such a thing.
because with docker it's easy to run a second container.
@CrazyWolf13 commented on GitHub (Jun 24, 2025):
dude, you are insanely quick, awesome :)
will test out as soon as release is up.
@arunavo4 commented on GitHub (Jun 24, 2025):
@CrazyWolf13 https://github.com/arunavo4/gitea-mirror/releases/tag/v2.19.0
@CrazyWolf13 commented on GitHub (Jun 24, 2025):
Startup of the service seems to fail for me after update.
@arunavo4 commented on GitHub (Jun 24, 2025):
@CrazyWolf13 are you using docker or Proxmox?
@CrazyWolf13 commented on GitHub (Jun 24, 2025):
Proxmox :)
@arunavo4 commented on GitHub (Jun 24, 2025):
@CrazyWolf13 I have made a patch update with some manual migrations. But will be releasing a breaking change major verison update with drizzle migrations for future proofing this.
Production build error fix:
Setup wizard on existing installation fix:
@CrazyWolf13 commented on GitHub (Jun 24, 2025):
Hi @arunavo4
Thanks for the quick fix, though that does not seem to resolve the issue, I still see the error:
Neither the update, nor the both snippets above seem to fix it :/
The first command did just a build no special output, but the service still showed the above error.
The second command looks promising, but seems to fail.
@arunavo4 commented on GitHub (Jun 24, 2025):
@CrazyWolf13 Hey I dont want to spend time writing migrations so I have moved the application to use drizzle migrations for easy migrations in the future but it does come with a major breaking change so just do a fresh start from scratch.
future migrations should be seemless.
v3.0.0I am currently testing this@CrazyWolf13 commented on GitHub (Jun 24, 2025):
alright.
Please let me know the most semless way to migrate the whole community-script userbase (Roughly 100 Installs)
Plus if we need to do any special changes to our deployment.
@CrazyWolf13 commented on GitHub (Jun 27, 2025):
@arunavo4 could you release v3 as an actual github release an tag it?
Seems like it's ony tagged on ghcr.
EDIT: seems like it's only prerelease.
@arunavo4 commented on GitHub (Jun 27, 2025):
It has issues so I have made pre release I need to fix the issues but I don't have time this week wait for next week I will try to find some time
@arunavo4 commented on GitHub (Jul 7, 2025):
Due to major issues I have removed the v3 branch and will update it once I have fully tested and fixed all the issues.
@arunavo4 commented on GitHub (Jul 17, 2025):
@CrazyWolf13 consider testing the latest v3 version
https://github.com/RayLabsHQ/gitea-mirror/releases/tag/v3.0.0
@CrazyWolf13 commented on GitHub (Jul 22, 2025):
@arunavo4 apologies for the delay, I was finally able to upgrade our script and also my personal instance. I fully reconfigured it too.
When clicking on the Authentification Part of that round bar, I end up with a black screen, I can't see anything in the log.
https://github.com/user-attachments/assets/9824c1bf-560d-4157-9b76-6ab0420cb4a5
@CrazyWolf13 commented on GitHub (Jul 22, 2025):
Error from dev-tools:
@CrazyWolf13 commented on GitHub (Oct 22, 2025):
I'm gonna close this as OIDC is implemented.