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

Authentication adapter should not know anything about authentication storage #513

Open
ojhaujjwal opened this issue Aug 11, 2014 · 5 comments

Comments

@ojhaujjwal
Copy link
Contributor

Authentication adapter should not know anything about authentication storage. See ZfcUser/Authentication/Adapter/Db.php#L111.

In restful applications, it is common these days not to use session but to use access tokens.

@ojhaujjwal
Copy link
Contributor Author

ping @Danielss89 , @Ocramius

@Ocramius
Copy link
Contributor

Absolute URI:

SessionContainer::getDefaultManager()->regenerateId();

@Ocramius
Copy link
Contributor

Yes, I agree here. This should probably be handled by the auth storage directly on write (if the storage value changes). It may be trivial to write a wrapper around a generic storage to do that.

@adamlundrigan
Copy link
Contributor

I've run into this with ZfcUser 1.2.x when trying to integrate with Apigility. Here's how I worked around it (module coming soon)

@EvanDotPro
Copy link
Member

Happened to be looking into this for something else. We could definitely make it easier to support this use-case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants