Download the PHP package mfc/oauth2 without Composer
On this page you can find all versions of the php package mfc/oauth2. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package oauth2
Short Description Generic OAuth2 authentication and authorization for TYPO3 CMS
License GPL-2.0-or-later
Homepage https://www.marketing-factory.de
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package oauth2
TYPO3 Extension oauth2 (mfc/oauth2)
This extension provides OAuth 2.0 authentication for TYPO3 installations.
1. Features
- Can automatically create new backend users
- Certain OAuth resource servers can control admin permissions and assign backend group memberships
2. Usage
1) Installation
The only way to install this extension is by using Composer. In your Composer based TYPO3 project root, just run composer require mfc/oauth2.
2) Configure the extension
To add an OAuth2 Server for login, we recommend you create your own little extension, use your existing site
package or put the configuration in your typo3conf/AdditionalConfiguration.php.
2.1) Using the GitLab Provider included in this extension
Configuring the GitLab Login Provider is pretty straight forward. Just put the following configuration into your ext_localconf.php
or the aforementioned typo3conf/AdditionalConfiguration.php and customize it to your needs.
You can obtain the required information for the provider by going to either https://gitlab.com/profile/applications if you're using the hosted version of GitLab, or to the equivalent page on your self-hosted GitLab server.
When creating the application within GitLab, you might need the following information:
- Redirect URI:
<your-domain-here>/typo3/index.php - Scopes:
api,read_user,openid
2.2 Creating your own provider
To create your own Provider, you need to create your own extension, and create a class which extends
Mfc\OAuth2\ResourceServer\AbstractResourceServer. You can then use the same boilerplate shown in 2.1 to register
your newly created provider. The arguments array included in the provider registration will be provided as-is as
the first argument to your providers constructor, with the addition of a providerName key which contains the identifier
you set in your registration.
Example
You've created your own extension, and created the class Just\AnExample\Providers\ExampleProvider.
To register your provider you'd extend the configuration as follows
The first argument passed to your provider will be:
3. License
mfc/oauth2 is released under the terms of the GPL-2 License.
All versions of oauth2 with dependencies
league/oauth2-client Version ^2.6
m4tthumphrey/php-gitlab-api Version ^11.13.0
omines/oauth2-gitlab Version ^3.4
php-http/guzzle7-adapter Version ^1.0
psr/http-factory Version ^1.0
typo3/cms-core Version ^12.2 || ^13.0 || dev-main
typo3/cms-beuser Version ^12.2 || ^13.0 || dev-main