Details
-
Story
-
Resolution: Fixed
-
High
-
Engineering tracked issues
-
Ventoux Sprint 1, Ventoux Sprint 2
-
4
Description
Currently user login is still handled by user/login legacy module. This prevents extensibility provided by Symfony security component to be properly exposed.
The following points should be considered:
- Once logged in Symfony stack, user must also be logged in legacy
- If logged in legacy (e.g. legacy_mode: true), authenticated user must be injected in the repository as well.
The following should be made possible as a follow up story:
- Login handlers (e.g. LDAP)
- SSO
Attachments
Issue Links
- blocks
-
EZP-22046 As a Site Visitor, I want user registration to be fully handled by Symfony
- Closed
-
EZP-22047 As a Site Visitor, I want user password retrieval to be fully handled by Symfony stack
- Closed
- relates to
-
EZP-21991 UserHash should be cached tied to user session id, not user cookies
- Closed
-
EZP-22005 REST API: when using sessions, is_logged_in cookie is always set for top-level domain, not for site root dir
- Closed
-
EZP-22157 Define a pagelayout for legacy modules in DemoBundle
- Closed
-
EZP-23169 eZ Publish allows invalid session name (not eZSESSID*)
- Closed
-
EZP-22500 Documentation: REST API Authentication requires is_logged_in cookie information
- Closed
-
EZP-23126 eZ Publish 5.3: redirect to /login on legacy mode returns module not found
- Closed
-
EZP-21528 As a DemoBundle user I want access to 5.x based login/logout functionality
- Closed
-
EZP-22081 As a developer, I want to be able to seamlessly use multiple user providers
- Closed
-
EZP-22145 Write documentation on login with Symfony stack
- Closed
-
EZP-22479 SiteAccessLimitation support for use in new login system
- Closed
- testing discovered
-
EZP-22159 DemoBundle legacy links not ready for user login/logout handled by Symfony stack
- Closed
- links to