PHPackages                             networkteam/neos-frontendlogin - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. networkteam/neos-frontendlogin

ActiveNeos-package

networkteam/neos-frontendlogin
==============================

A Neos package for building up member areas with frontend login

1.5.0(1y ago)420.8k↓50%4[2 issues](https://github.com/networkteam/Networkteam.Neos.FrontendLogin/issues)GPL-3.0-or-laterPHP

Since Nov 29Pushed 1y ago4 watchersCompare

[ Source](https://github.com/networkteam/Networkteam.Neos.FrontendLogin)[ Packagist](https://packagist.org/packages/networkteam/neos-frontendlogin)[ RSS](/packages/networkteam-neos-frontendlogin/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (10)Dependencies (2)Versions (17)Used By (0)

Networkteam.Neos.FrontendLogin
==============================

[](#networkteamneosfrontendlogin)

Neos package for frontend login inspired by [Flowpack.Neos.FrontendLogin](https://github.com/Flowpack/Flowpack.Neos.FrontendLogin). It provides a mixin for MemberAreaRootPages. The package makes use of the `accessRoles` property of `NodeInterface`.

**Note:** It seems that the current Neos versions `neos/neos:7.*` and `neos/neos:8.*` are compatible with this package as the deprecated parts are not yet removed. But be aware of breaking changes in the near future.

Features
--------

[](#features)

- Place a MemberAreaRootPage within your page tree and all pages beneath it including the member area page itself will be protected
- Configure redirect page after login and logout
- Redirect to configured login form when a protected page is requested without valid login. After successful login you will be redirected to initially requested page (referer).
- Multiple member areas with different access roles are possible

Installation
------------

[](#installation)

Install the package via composer

```
composer require networkteam/neos-frontendlogin
```

Campatibility with `neos/neos` Package

Neos.NeosNetworkteam.Neos.FrontendLogin`4.*``1.3.*``5.*``1.4.*``7.*``1.4.*``8.*``1.5.*`Migration
---------

[](#migration)

This package provides a node migration for copying existing internal accessRoles values to a regular node property.

```
./flow node:migrate 20210419111000 --confirmation true
```

NodeTypes
---------

[](#nodetypes)

**Networkteam.Neos.FrontendLogin:Mixins.MemberAreaRoot**

The mixin `Networkteam.Neos.FrontendLogin:Mixins.MemberAreaRoot` defines the root point of a specific member area and is of type `Neos.NodeTypes:Page`

Authentication via roles
------------------------

[](#authentication-via-roles)

This packages makes use of the neos flow security framework. For further details you can have a look into the [documentation of the flow framework](https://flowframework.readthedocs.io/en/stable/TheDefinitiveGuide/PartIII/Security.html?highlight=roles#defining-privileges-policies).

Two role definitions are provided:

- **Networkteam.Neos.FrontendLogin:MemberArea** (abstract): Interface for MemberArea roles. It is used within access role selection of MemberAreaRootPages.
- **Networkteam.Neos.FrontendLogin:FrontendUser**: Concrete access role implementation

You can define your own frontend user roles by adding them to the `Policy.yaml` of your package. Make sure that you add `Networkteam.Neos.FrontendLogin:MemberArea` as parent role. Otherwise, you won't be able to select the role within MemberAreaRootPage node.

When you set access roles on your MemberAreaRootPage via the inspector and apply the changes, these access roles will be set on all DocumentNodes beneath that MemberAreaRootPage as well. This ensures that all these pages can only be access by users having one of the selected roles.

Create Frontend Users
---------------------

[](#create-frontend-users)

To create a new Frontend User you can use the `neos.neos:user:create` command, e.g.

```
./flow user:create --authentication-provider "Networkteam.Neos.FrontendLogin:Frontend" --roles "Networkteam.Neos.FrontendLogin:FrontendUser"
```

or use the user management module inside Neos backend.

Create member area
------------------

[](#create-member-area)

The package does not supply a concrete implementation. It does only supply a mixin. To create a member area you need to define a specific nodeType for MemberAreaRootPages which implements the mixin provided by this package.

### Define your nodeTypes

[](#define-your-nodetypes)

You need to define one nodeType for MemberAreaRootPages.

An example configuration could look as follows:

*Packages/Application/Your.Package/Configuration/NodeTypes.MemberAreaRootPage.yaml*

```
'Your.Package:MemberAreaRootPage':
  superTypes:
    'Neos.Neos:Document': true
    'Networkteam.Neos.FrontendLogin:Mixins.MemberAreaRoot': true
  ui:
    label: 'Member area'
```

### Define fusion object

[](#define-fusion-object)

For your defined nodeType you need a suitable fusion object. An example configuration could look as follows:

*Packages/Application/Your.Package/Resources/Private/Fusion/MemberAreaRootPage.fusion*

```
# MemberAreaRootPage
prototype(Your.Package:MemberAreaRootPage) < prototype(Neos.Neos:Page) {

}

```

**Hint:** Usually you would inherit from the default page prototype of your site package.

### Add pages and login form

[](#add-pages-and-login-form)

Now you can log into Neos backend and create a new **MemberAreaRootPage**. Define which users should have access to this member area by selecting access roles and apply the changes.

Next you need to add a **login form** on a page which is not protected. Do not place the login form within your member area or the MemberAreaRootPage. Otherwise, your users won't be able to access the login form.

Now go back to the previously created MemberAreaRootPage and select the page containing the login form ( `Login form page`).

Additionally, you can add further pages beneath your MemberAreaRootPage. They will be protected.

Adding your own MemberArea roles
--------------------------------

[](#adding-your-own-memberarea-roles)

If you define your own MemberArea roles via `Policy.yaml`, make sure that you add them as `parentRoles` to `Neos.Neos:AbstractEditor` role definition. Otherwise pages only having your new roles will not be visible in Neos backend. This could also lead to error during publishing.

**Policy.yaml**

```
roles:
  'Your.Package:UserWithFrontendAccess':
    parentRoles: [ 'Networkteam.Neos.FrontendLogin:MemberArea' ]

  'Neos.Neos:AbstractEditor':
    parentRoles: [ 'Your.Package:UserWithFrontendAccess' ]
```

Password reset
--------------

[](#password-reset)

To give your frontend users the possibility to reset there password you can install and use the package [Networkteam.Neos.PasswordReset](https://github.com/networkteam/Networkteam.Neos.PasswordReset).

Translation
-----------

[](#translation)

To translate the login error message or login form labels create a xliff file for each language in your package and set properties `original="Main"` and `product-name="Networkteam.Neos.FrontendLogin"` on `` tag. Now you can override the language keys from the original translation file of `Networkteam.Neos.FrontendLogin` package you like.

```

                Enter your username

                Enter your password

                Authentication failed!The login could not be performed with the given credentials.]]>

```

###  Health Score

39

—

LowBetter than 86% of packages

Maintenance24

Infrequent updates — may be unmaintained

Popularity33

Limited adoption so far

Community18

Small or concentrated contributor base

Maturity69

Established project with proven stability

 Bus Factor2

2 contributors hold 50%+ of commits

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~161 days

Recently: every ~311 days

Total

14

Last Release

629d ago

Major Versions

0.9.0 → 1.0.02018-12-20

### Community

Maintainers

![](https://www.gravatar.com/avatar/7cbf52f8dce27737b73b79ac2c958434339f3dcf704b17a040956ed9a33eb4ef?d=identicon)[networkteam](/maintainers/networkteam)

---

Top Contributors

[![networkteamcom](https://avatars.githubusercontent.com/u/31891264?v=4)](https://github.com/networkteamcom "networkteamcom (5 commits)")[![ger4003](https://avatars.githubusercontent.com/u/1758522?v=4)](https://github.com/ger4003 "ger4003 (2 commits)")[![hlubek](https://avatars.githubusercontent.com/u/33351?v=4)](https://github.com/hlubek "hlubek (1 commits)")[![monofone](https://avatars.githubusercontent.com/u/373163?v=4)](https://github.com/monofone "monofone (1 commits)")[![networkteam-lange](https://avatars.githubusercontent.com/u/19548950?v=4)](https://github.com/networkteam-lange "networkteam-lange (1 commits)")[![nilsjung](https://avatars.githubusercontent.com/u/24273394?v=4)](https://github.com/nilsjung "nilsjung (1 commits)")[![Sebobo](https://avatars.githubusercontent.com/u/596967?v=4)](https://github.com/Sebobo "Sebobo (1 commits)")

### Embed Badge

![Health badge](/badges/networkteam-neos-frontendlogin/health.svg)

```
[![Health](https://phpackages.com/badges/networkteam-neos-frontendlogin/health.svg)](https://phpackages.com/packages/networkteam-neos-frontendlogin)
```

###  Alternatives

[neos/neos-ui

Neos CMS UI written in React

2661.0M104](/packages/neos-neos-ui)[neos/neos

An open source Content Application Platform based on Flow. A set of core Content Management features is resting within a larger context that allows you to build a perfectly customized experience for your users.

116989.0k674](/packages/neos-neos)[sitegeist/kaleidoscope

Responsive-images for Neos

29352.4k10](/packages/sitegeist-kaleidoscope)[sandstorm/neostwofactorauthentication

1223.6k](/packages/sandstorm-neostwofactorauthentication)[neos/seo

SEO configuration and tools for Neos

13990.5k24](/packages/neos-seo)[neos/form-builder

Flow Form Framework integration into Neos CMS

19347.1k18](/packages/neos-form-builder)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
