Page Contents
The following pages are tagged with
| Title | Excerpt | |
|---|---|---|
| ACL REST API | The ACL model connects principals to protected resources. The system grants permissions to principals (users or applications, that can be grouped into roles). | |
| ACL generator | Important: Before running this generator, you must create an application using the application generator. Then you must run the command from the root directory of the application. Synopsis Adds a new access control list (ACL) entry to a LoopBack application. Access token REST API |
The built-in access token model represents the access token that LoopBack creates for an authenticated user. |
| Access token invalidation | When a user changes their email or password, other sessions are logged out for security reasons. | |
| Authentication, authorization, and permissions | LoopBack includes built-in token-based authentication. | |
| Controlling data access | LoopBack uses access control lists (ACLs) to control who can access what data. | |
| Logging in users | The built-in User model provides methods to log in a user, log out a user, and reset a user's password. | |
| Managing users | LoopBack's built-in User model provides essential user management features. | |
| Registering users | The built-in User model provides methods to register new users and confirm their email addresses. | |
| Role REST API | The built-in Role model represents a set of access controls that can apply to a specific user. |