Download the PHP package xima/xima-oauth2-extended without Composer

On this page you can find all versions of the php package xima/xima-oauth2-extended. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of xima/xima-oauth2-extended

Informations about the package xima-oauth2-extended

XIMA OAuth2 Extended

TYPO3 extension that extends the functionality of waldhacker/ext-oauth2-client for on-the-fly user creation.

New resource provider

TYPO3 user creation

To create frontend or backend users from OAuth2 authentication, you can create your own ResourceResolver by implementing the ResourceResolverInterface and register it in the extension configuration:

Available resource resolver

This TYPO3 extension provides a resource resolver to facilitate the creation and updating of TYPO3 users through OAuth2 login. The resource resolver serves as a mapping tool for data retrieval from various OAuth resources. While the default resolver, GenericResolver, covers most OAuth endpoints, each endpoint's unique API for extended user information might require specific handling, leading to variations in features.

Resolver User Creation Profile picture Group Creation
GenericResourceResolver ✅ 🚫 🚫
MicrosoftResourceResolver ✅ ✅ (BE only) ✅ (BE only)
AuthentikResourceResolver ✅ ✅ (BE only) 🚫
GitlabResourceResolver ✅ 🚫 🚫

Extended resource resolver options

The extension provides customizable options to tailor the resolver's behavior:

Option Description Default
resolverClassName Class name of the resource resolver. See above for list of available resolver GenericResourceResolver::class
createBackendUser If set, create a new TYPO3 backend user if no existing user is authenticated false
createFrontendUser If set, create a new TYPO3 frontend user if no existing user is authenticated false
defaultBackendUsergroup List of be_group UIDs the created user will be assigned to
defaultFrontendUsergroup List of fe_group UIDs the created user will be assigned to
createBackendUsergroups If set, create backend user groups based on those of the remote user false
createFrontendUsergroups If set, create frontend user groups based on those of the remote user false
requireBackendUsergroup If set, require the remote user to be in at least one user group with matching oauth2_id false
requireFrontendUsergroup If set, require the remote user to be in at least one user group with matching oauth2_id false
imageStorageBackendIdentifier Storage identifier for downloaded backend user profile images 1:/user_upload/oauth
imageStorageFrontendIdentifier Storage identifier for downloaded frontend user profile images 1:/user_upload/oauth
defaultBackendLanguage Language identifier for created backend users default
defaultBackendAdminGroups Comma separated list of remote oauth2_ids that will become Admin during login. Special value all.

FAQ

Register Return-URLs For the backend login the return url looks like this: Replace `domain.de` and `yourProviderId` with your data!
Login not working Make sure `cookieSameSite` is set to `lax`.
Order of login provider To change the order of provider displayed at the `/typo3` login page (OAuth login over classic username/password), use the following snippet:

All versions of xima-oauth2-extended with dependencies

PHP Build Version
Package Version
Requires php Version >=8.2
ext-pdo Version *
co-stack/typo3-oauth2-client Version ^3.0 || ^4.0
league/oauth2-client Version >=2.7
typo3/cms-core Version ^12.4 || ^13.4
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package xima/xima-oauth2-extended contains the following files

Loading the files please wait ....