[Flow] Policy.yaml - Could not authenticate any token

[Stefan Bruggmann]

Hi Bastian

Quote: Bastian Waidelich (bwaidelich) wrote on Tue, 02 June 2015 14:08
> Nice feature! ;)

thanks :)


> One feature of Flows Security Framework is that multiple accounts can be 
> authenticated at the same time. In order to define which authentication 
> provider should be involved, those can be bound to so called 
> "RequestPatterns".

Ah ok, I think now I got this doc section..

> If you include your controller to that pattern in your packages 
> Settings.yaml, everything should work as expected:
> 
> TYPO3:
>    Flow:
>      security:
>        authentication:
>          providers:
>            'Typo3BackendProvider':
>              requestPatterns:
>                controllerObjectName: 
> 'TYPO3\Neos\Controller\.*|TYPO3\Neos\Service\.*|TYPO3\Media\Controller\.*|WebExcess\Notifications\Controller\NotificationController'

That did not work.
After some unsuccsessful tests with a NeosRequestPattern.php, like it's done in Flowpack.Neos.FrontendLogin I checked the Configuration..

/flow configuration:validate
Settings.TYPO3.Flow.security.authentication.providers.Typo3BackendProvider.requestPatterns.Flowpack\Neos\FrontendLogin\Security\NeosRequestPattern -> This property is not allowed here, check the spelling if you think it belongs here.
Settings.TYPO3.Flow.security.authentication.providers.Typo3BackendProvider.label -> This property is not allowed here, check the spelling if you think it belongs here.
Settings.TYPO3.Flow.security.authentication.providers.Flowpack.Neos.FrontendLogin:Frontend.requestPatterns.Flowpack\Neos\FrontendLogin\Security\NeosRequestPattern -> This property is not allowed here, check the spelling if you think it belongs here.

So I deactivated Flowpack.Neos.FrontendLogin (Release 1.0.1) and my Plugin works now! Thanks! :)

But the result of
/flow configuration:show --type Settings --path TYPO3.Flow.security.authentication.providers
was ok.
Just that it was ignored.

--
Stefan