Extends fof/oauth for login with Gitea or Forgejo
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Kris 0e880dffc3 remove translation 2 months ago
resources Delete 'resources/locale/de.yml' 2 months ago
src Corr2 2 years ago
LICENSE.md Init 2 years ago
README.md remove translation 2 months ago
composer.json fixed dependencies 2 years ago
extend.php Changed comment (remove FoF) 2 years ago

README.md

OAuth2 for Gitea or Forgejo

A supplement to the OAuth2 extenstion fof/oauth by FriendsOfFlarum

License

A Flarum extension supplementing fof/oauth (OAuth for Flarum by FriendsOfFlarum) with a lean implementation for community owned Gitea or Forgejo instances.

Based on frie/flarum-nextcloud-oauth, work in progress!

Installation

composer require povoq/flarum-gitea-oauth

Updating

composer update povoq/flarum-gitea-oauth

Configuration

Before activating this extension, fof/oauth also needs to be activated.

The Gitea/Forgejo provider is configured in the scope of fof/oauth

Configuration for Gitea or Forgejo

Gitea authentication is somewhat different from authentication against Github, Twitter etc.: we usually have community-owned Gitea instances, which we supplement by a commmunity-owned discussion forum. So it makes sense to enable enforcement of identical user names and nicknames (by configuration).

Therefore a switch was added Copy user name from Gitea (activate by entering yes in the input field). Without activating this switch the user has to define the user name on registration as usual - when activated the username is copied from Gitea. Since there is no Gitea or Forgejo icon yet in the awesome brand collection, the icon can be set by another input field.