Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to set the Authentication storage #84

Open
visto9259 opened this issue Jun 26, 2024 · 4 comments
Open

Add option to set the Authentication storage #84

visto9259 opened this issue Jun 26, 2024 · 4 comments
Labels
enhancement New feature or request V4 To be implemented in version 4

Comments

@visto9259
Copy link
Member

Currently, the authentication service is configured with a LmcUser\Authentication\Storage\Db storage.

Add a module options to define the storage service to use by the Authentication service, with the default being LmcUser\Authentication\Storage\Db.

This will enable the usage of other storage services, including the storage services available from laminas-autentication

@visto9259 visto9259 added enhancement New feature or request V4 To be implemented in version 4 labels Jun 26, 2024
@tyrsson
Copy link

tyrsson commented Oct 4, 2024

Not sure if it currently does or not, but you might want to consider setting up a custom session container as well so as to change the namespace to LmcUser_Auth so as to give a visual indicator (in the session data) that the standard container is not being used. It would also further unify sessions for LmcUser. I would also suggest possibly providing explicit factories for all the related session components so as to insure that the default manager is never used.

@visto9259
Copy link
Member Author

visto9259 commented Oct 8, 2024

@tyrsson
Currently, LmcUser\Authentication\Storage\Db uses Laminas\Authentication\Storage\Session which defaults to the 'Laminas_Auth' session container.
Authentication adapters in LmUser then use session containers using the LmcUserNamespace namespace. This container is not used by the Laminas\Authentication\Service.

I would also suggest possibly providing explicit factories for all the related session components so as to insure that the default manager is never used

Can you expand on NEVER using the default manager? Are you talking about the default Laminas session manager? LmcUser does not provide a factory to create the session manager, it is up to the user to provide and start it. Is this what you are talking about?

@tyrsson
Copy link

tyrsson commented Oct 9, 2024

Yes, sorry. That is what I was referring too.

@visto9259
Copy link
Member Author

Then can you expend on never using the default manager? Why not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request V4 To be implemented in version 4
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants