Codeigniter integrated Tank Auth permission library detailed explanation_PHP tutorial

Intersect with other CodeIgniter class libraries, tank_auth, which is simple to configure and easy to use, and the author has been updating it. It is now 1.0.9. 1.0.8 already supports CI2.0. I use it for most projects now. It is therefore recommended to everyone.

Steps to install Tankauth

Download the latest version of the class library (Download address: http://www.konyukhov.com/soft/tank_auth/tank_auth.zip)

Unzip the file
Copy the corresponding files under application to your CIapplication folder.
Copy the captcha folder to your CI folder (the project directory, the same directory as the application). And make sure the directory is writable under the web server.
Install the database (schema.sql file) structure in your MySQL database.
Open the application/config/config.php file under your CI project and change the value of $config['sess_use_database'] to TRUE.
The installation is complete!

If the following error occurs during access:

AnErrorWasEncountered
InordertousetheSessionclassyouarerequiredtosetanencryptionkeyinyourconfigfile.

This error message requires a key. Then open config.php and add a key after $config['encryption_key'].

TankAuth official website address: http://www.konyukhov.com/soft/tank_auth/

If an error occurs, don’t forget to look at the configuration files (tank_auth.php and email.php). After the installation is complete, the class library should work perfectly, but depending on the conditions of your server and your needs, it is best to have options Modify it sexually.

Tip: By default, the strong system-specific password hashes generated by the library are not portable. This means that once created, the user database cannot be exported and imported into other databases. This feature can also be configured File modification.

A brief description of the Tankauth class library

The class library uses the MVC model, which means that all database-related methods are encapsulated in model files, and the class library itself also serves as the interface for these methods. The controller (auth) makes the relevant request and calls the method in the class library to render the corresponding view (displayed in the browser or sent by email). The controller contains the following methods:

login: User logs into the website. If the login is successful and the user account is active, the user will be redirected to the homepage. If not activated, send_again will be called (see below). If login fails, the user will remain on the same page (login page);
logout: log out the user.
register: Register users to the website. If registration is successful, a user account will be created. If the value of the email_activation item in the configuration file is set to TRUE, the user needs to activate the account by clicking on the special link sent to the email; otherwise it is activated by default. Please note: After registration, the user has not passed the login verification and still needs to log in.
send_again: Send activation email to the same or new email address again. This method is called every time when logged in as an active user. This function is very useful when the user does not receive the mail due to mailbox problems or wrong emial address. Users can change their email or keep it the same.
activate: Activate user account. Usually this method is activated by clicking a link in the email. You can activate the account by clicking "forgotpassword" and entering your email. The user is authenticated via the user's ID and verification code in the URL.
forgot_password: Generate a special reset code (in order to change the password) and send it to the user. Obviously users will only use this method when they forget their password.
reset_password: Replace the old (forgotten) password with a new (user-set) password. This method can be called by clicking on the link in the email. The user is authenticated via the user's ID and verification code in the URL.
change_password: "Normal" password change (vs. password reset). It can only be called when the user is logged in and activated. To ensure security, user secrets still need to be verified.
change_email: Modify the user's email. It can only be called when the user is logged in and activated. To ensure security, user secrets still need to be verified. This new email can only be activated by clicking on the link sent to this email.
reset_email: Activate the new email address and replace it with a new one. This method can be called by clicking a link in the email. The user is authenticated via the user's ID and verification code in the URL.
unregister: Delete user account. It can only be called when the user is logged in and activated. To ensure security, user secrets still need to be verified.

Since the auth controller manages all user methods (including login and logout), you do not necessarily have to directly call methods in the class library. But the following must be called:

is_logged_in: Check whether the user is logged in to the website.
get_user_id: If the user is logged in, get the user ID, otherwise return FALSE.
get_username: Get the username of the authenticated user, otherwise return FALSE. If the username is not registered, calling this method is meaningless (any user will return an empty string at this time).