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 | 重要： この生成ツールを実行する前に、application generator を使ってアプリケーションを作成する必要があります。 また、アプリケーションの最上位ディレクトリからコマンドを実行しなければなりません。 Synopsis Adds a new access control list (ACL) entry to a LoopBack application. lb acl [options] With IBM API Connect developer toolkit: apic loopback:acl [options] With legacy... |
| Access token REST API | The built-in access token model represents the access token that LoopBack creates for an authenticated user. |
| 認証・認可・パーミッション | LoopBack は組み込みのトークンに基づく認証が含まれています。 |
| Configuring providers.json | Overview Use the providers.json file (in the project root directory) to configure third-party login using loopback-component-passport. This file contains settings for each third-party authorization provider, in provider and provider-link objects (for example, google-login and google-link). To load the configuration, add code such as the following to |
| 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. |
| Third-party login using Passport | Use the LoopBack Passport component to enable third-party login, so users can log in using existing accounts such as Facebook, Google, Twitter, Github, and i... |
| Tutorial: third-party login | A tutorial on setting up authentication using Passport. |