AutoLogin - GitLite

KO | EN

gitlite — search

#javascript #react #ai #golang #go #android #rust #linux #docker #windows #awesome #awesome-list #vue #pytorch

AutoLogin

(★ 99)

Faciliates automatic login via a single token for Symfony's Security component.

파일 탐색기

최종 버전 다운로드 (.zip)

- - tests.yml
- - AlreadyAuthenticatedEvent.php
- - AutoLoginTokenNotFoundException.php
- - AutoLoginUserProviderInterface.php
- AutoLoginEvents.php
.gitignore
composer.json
LICENSE
phpunit.xml.dist
README.md

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/jmikola/AutoLogin

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd AutoLogin

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. PHP (Composer)

쉬움 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
PHP PHP 실행 환경이 필요합니다.
Composer PHP 라이브러리 설치를 위한 패키지 매니저입니다.

$ composer require jmikola/auto-login

이 명령어를 터미널에 그대로 입력해 실행하세요.

✅ php -S localhost:8000 같은 내장 서버로 실행한 뒤 브라우저에서 http://localhost:8000 으로 접속해보세요.

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# AutoLogin

This library implements a Symfony security firewall listener to authenticate
users based on a single query parameter. This is useful for providing one-click
login functionality in email and newsletter links.

## Installation

The library is published as a [package][] and is installable via [Composer][]:

```
$ composer require jmikola/auto-login
```

[package]: https://packagist.org/packages/jmikola/auto-login
  [Composer]: http://getcomposer.org/

### Compatibility

This library requires Symfony 4.3 or above.

## Usage

This library implements authentication provider and firewall listener classes,
which may be plugged into Symfony's security component to intercept requests
and automatically authenticate users based on a single request parameter.

To utilize this library in a full-stack Symfony application, you may want to
use [JmikolaAutoLoginBundle][]. An example of registering an authentication
provider and firewall listener manually may be found in the
[Security component documentation][].

[JmikolaAutoLoginBundle]: https://github.com/jmikola/JmikolaAutoLoginBundle
  [security component documentation]: http://symfony.com/doc/current/components/security/firewall.html

### Token

When a user is automatically logged in by a token parameter in the request, they
will be authenticated with an `AutoLoginToken` instance. In the context of
authorization, this token satisfies `IS_AUTHENTICATED_FULLY`. Ideally, it would
be possible to restrict the token to `IS_AUTHENTICATED_REMEMBERED`, but that is
not yet supported. Additional information on these authorization levels may be
found in Symfony's [authorization documentation][].

[authorization documentation]: http://symfony.com/doc/current/components/security/authorization.html

### Events

The firewall listener may dispatch events if constructed with an
[event dispatcher][] instance.

[event dispatcher]: http://symfony.com/doc/current/components/event_dispatcher/introduction.html

#### Interactive Login

Upon successful authentication by a token parameter in the request, an
interactive login core event will be dispatched with the authenticated
`AutoLoginToken` instance.

#### Already Authenticated

*This event was contributed by [Antonio Trapani][] in [PR #9][].*

If a token parameter is present in the request, but the user is already
authenticated, a custom event will be dispatched, which includes the token's
value. After dispatching this event, the listener's default behavior is to
return immediately, since there is likely no work to be done.

A practical use for this event would be to mark a user's email addresses as
confirmed, assuming the auto-login link with the token was only delivered via
email. As a business requirement, the confirmation service might also listen to
the interactive login core event and operate when the authenticated token was an
`AutoLoginToken` instance.

**Note:** Unlike the interactive login event, the token parameter in this event
will not have been validated. It will be the responsibility of the listener to
check whether it matches the currently authenticated user. For this reason, it
may be helpful to inject this library's provider class.

[Antonio Trapani]: https://github.com/TwistedLogic
  [PR #9]: https://github.com/jmikola/AutoLogin/pull/9

#### Overriding Already Authenticated Users

*This feature was contributed by [Mathieu Gauthier-Lafaye][] in [PR #10][].*

By default, the listener will only dispatch an event if the user is already
authenticated; it does not override the existing authenticated user. In some
cases, it may be desirable to allow an auto-login link to override an existing
authenticated user. Otherwise, the user would first need to log out before using
the auto-login link. Setting the listener's `override_already_authenticated`
boolean option to `true` will enable this behavior.

[Mathieu Gauthier-Lafaye]: https://github.com/gauthierl
  [PR #10]: https://github.com/jmikola/AutoLogin/pull/10