Download the PHP package topshelfcraft/legacy-login without Composer

On this page you can find all versions of the php package topshelfcraft/legacy-login. 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 topshelfcraft/legacy-login

Informations about the package legacy-login

Legacy Login

Seamless legacy user authentication for Craft CMS

A Top Shelf Craft creation
Michael Rog, Proprietor

TL;DR.

The Legacy Login plugin provides a way to authenticate users from a legacy system into your Craft CMS site.

The legacy-login/login custom action stands in for Craft's native login form action. If a submitted loginName/password fails Craft's native authentication, the plugin checks the legacy system(s) and tries to authenticate a user from there. If a matching legacy user is found and authenticated, the plugin creates or updates the User in Craft and logs into the newly created/matched account.

What legacy systems are supported?

Legacy Login provides drivers for authenticating legacy users from:

Two legacy drivers are not yet ported to the Craft 4 version of Legacy Login:

Installation

  1. From your project directory, use Composer to require the plugin package:

    Note: Legacy Login is also available for installation via the Craft CMS Plugin Store.

  2. In the Control Panel, go to Settings → Plugins and click the “Install” button for Legacy Login.

  3. Finally, add the Legacy Login form to your login template. The template follows the same design as Craft's native login form, except the form action should point to the LegacyLoginController rather than Craft's native UsersController:

Configuration

To customize the plugin's behavior, add a legacy-login.php file to your Craft config directory:

The file should return an array, following the same format as Craft's own Config files.

(As with all Config files in Craft, the Legacy Login config supports Multi-Environment Configs and other techniques for Environmental Configuration.)

handlers

The config file provides a list of Handler configurations.

Each Handler configuration must define a name and type.

Available options include:

name

What the handler should be called in Legacy Login records.

type

'Craft4', 'Craft3', 'Craft2', 'EE2', 'BigCommerce', 'Wellspring', 'WordPress', or a custom (fully qualified) class name.

createUser

Whether to create a new Craft user if a matching one doesn't already exist in the system.

(If false, only existing Users can be logged in via legacy handlers. Authentication for legacy users that don't match a User in the current system will fail, whether the loginName/password are correct or not.)

Default: true

updateUser

Whether to update the profile (including password) of a matched Craft user from the legacy data.

Default: true

requirePasswordReset

Whether to set the Require Password Reset flag on a created/matched Craft user, i.e. requiring them to change their password upon their next login.

Default: false

maxLogins

How many times a User may be authenticated using this handler.

Default: 1

table

For database-type handlers: The name of the table from which legacy user data should be queried.

db

For database-type handlers: An array of database config options, following the same template as Craft's own Database Connection Settings.

What are the system requirements?

Craft 4.0+ and PHP 8.0+

I found a bug.

I'm not surprised... Legacy Login is still in beta. Please open a GitHub Issue or submit a PR.

Contributors:

All versions of legacy-login with dependencies

PHP Build Version
Package Version
Requires craftcms/cms Version ^4.2.1
topshelfcraft/base Version ^4.0.1
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 topshelfcraft/legacy-login contains the following files

Loading the files please wait ....