Go to file
Earl Warren 7cabc5670d
Implement remote user login source and promotion to regular user
A remote user (UserTypeRemoteUser) is a placeholder that can be
promoted to a regular user (UserTypeIndividual). It represents users
that exist somewhere else. Although the UserTypeRemoteUser already
exists in Forgejo, it is neither used or documented.

A new login type / source (Remote) is introduced and set to be the login type
of remote users.

Type        UserTypeRemoteUser
LogingType  Remote

The association between a remote user and its counterpart in another
environment (for instance another forge) is via the OAuth2 login
source:

LoginName   set to the unique identifier relative to the login source
LoginSource set to the identifier of the remote source

For instance when migrating from GitLab.com, a user can be created as
if it was authenticated using GitLab.com as an OAuth2 authentication
source.

When a user authenticates to Forejo from the same authentication
source and the identifier match, the remote user is promoted to a
regular user. For instance if 43 is the ID of the GitLab.com OAuth2
login source, 88 is the ID of the Remote loging source, and 48323
is the identifier of the foo user:

Type        UserTypeRemoteUser
LogingType  Remote
LoginName   48323
LoginSource 88
Email       (empty)
Name        foo

Will be promoted to the following when the user foo authenticates to
the Forgejo instance using GitLab.com as an OAuth2 provider. All users
with a LoginType of Remote and a LoginName of 48323 are examined. If
the LoginSource has a provider name that matches the provider name of
GitLab.com (usually just "gitlab"), it is a match and can be promoted.

The email is obtained via the OAuth2 provider and the user set to:

Type        UserTypeIndividual
LogingType  OAuth2
LoginName   48323
LoginSource 43
Email       foo@example.com
Name        foo

Note: the Remote login source is an indirection to the actual login
source, i.e. the provider string my be set to a login source that does
not exist yet.
2024-04-25 13:03:49 +02:00
.devcontainer
.forgejo test(ldap): add LDAP tests 2024-04-24 22:06:32 +02:00
.gitea
assets
build s/Gitea/Forgejo in various log messages and comments 2024-04-21 21:26:15 +05:00
cmd fix(cli): admin user create first user never require a password change 2024-04-24 15:43:27 +02:00
contrib
custom/conf Fixup app.example.ini for task section, which is now queue.task (#30555) 2024-04-21 16:28:16 +02:00
docker
models Implement remote user login source and promotion to regular user 2024-04-25 13:03:49 +02:00
modules [FEAT]Add Option to hide Release Archive links (#3139) 2024-04-24 15:15:55 +00:00
options [FEAT]Add Option to hide Release Archive links (#3139) 2024-04-24 15:15:55 +00:00
public
releases/images
routers Implement remote user login source and promotion to regular user 2024-04-25 13:03:49 +02:00
services Implement remote user login source and promotion to regular user 2024-04-25 13:03:49 +02:00
templates [FEAT]Add Option to hide Release Archive links (#3139) 2024-04-24 15:15:55 +00:00
tests Implement remote user login source and promotion to regular user 2024-04-25 13:03:49 +02:00
tools
web_src UI: fix rounding of vertical menus on /issues, /pulls 2024-04-24 19:07:16 +05:00
.air.toml Kill all gitea processes before air build (#30477) 2024-04-21 11:38:58 +02:00
.changelog.yml
.deadcode-out [DEADCODE] update 2024-04-21 16:40:43 +02:00
.dockerignore
.editorconfig
.eslintrc.yaml
.gitattributes
.gitignore
.gitmodules cleanup(tests): remove manual testing submodule 2024-04-21 10:13:51 +02:00
.gitpod.yml
.golangci.yml
.ignore
.markdownlint.yaml
.npmrc
.spectral.yaml
.yamllint.yaml
BSDmakefile
build.go
CODEOWNERS
CONTRIBUTING.md
DCO
Dockerfile fix(release): add missing ARG RELEASE_VERSION 2024-04-17 17:16:53 +02:00
Dockerfile.rootless
go.mod
go.sum
LICENSE
main.go
MAINTAINERS
Makefile Add a few root files to lint-spell (#30530) 2024-04-21 16:28:16 +02:00
package-lock.json Update dependency vitest to v1.5.1 2024-04-25 06:03:55 +00:00
package.json Update dependency vitest to v1.5.1 2024-04-25 06:03:55 +00:00
playwright.config.js
poetry.lock
poetry.toml
pyproject.toml
README.md
RELEASE-NOTES.md Merge pull request 'api: The repo wiki APIs should respect WikiBranch' (#3430) from algernon/forgejo:master-of-branches into forgejo 2024-04-25 05:37:25 +00:00
renovate.json chore(renovate): require more approvals 2024-04-24 13:47:54 +02:00
stylelint.config.js
tailwind.config.js
updates.config.js
vitest.config.js
webpack.config.js

Welcome to Forgejo

Hi there! Tired of big platforms playing monopoly? Providing Git hosting for your project, friends, company or community? Forgejo (/for'd͡ʒe.jo/ inspired by forĝejo the Esperanto word for forge) has you covered with its intuitive interface, light and easy hosting and a lot of builtin functionality.

Forgejo was created in 2022 because we think that the project should be owned by an independent community. If you second that, then Forgejo is for you! Our promise: Independent Free/Libre Software forever!

What does Forgejo offer?

If you like any of the following, Forgejo is literally meant for you:

  • Lightweight: Forgejo can easily be hosted on nearly every machine. Running on a Raspberry? Small cloud instance? No problem!
  • Project management: Besides Git hosting, Forgejo offers issues, pull requests, wikis, kanban boards and much more to coordinate with your team.
  • Publishing: Have something to share? Use releases to host your software for download, or use the package registry to publish it for docker, npm and many other package managers.
  • Customizable: Want to change your look? Change some settings? There are many config switches to make Forgejo work exactly like you want.
  • Powerful: Organizations & team permissions, CI integration, Code Search, LDAP, OAuth and much more. If you have advanced needs, Forgejo has you covered.
  • Privacy: From update checker to default settings: Forgejo is built to be privacy first for you and your crew.
  • Federation: (WIP) We are actively working to connect software forges with each other through ActivityPub, and create a collaborative network of personal instances.

Learn more

Dive into the documentation, subscribe to releases and blog post on our website, find us on the Fediverse or hop into our Matrix room if you have any questions or want to get involved.

Get involved

If you are interested in making Forgejo better, either by reporting a bug or by changing the governance, please take a look at the contribution guide.