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

Any plans on basing this servant-auth? #41

Open
jwoudenberg opened this issue Nov 19, 2017 · 1 comment
Open

Any plans on basing this servant-auth? #41

jwoudenberg opened this issue Nov 19, 2017 · 1 comment

Comments

@jwoudenberg
Copy link

Hey there! Thanks for your efforts in writing this library!

I've been reading a bit and noticed servant will probably deprecate it's auth support in favour of haskell-servant/servant-auth. I was wondering if you had any plans to migrate this library to this new auth system.

I'd like to switch to auth-servant since it seems it will become the default authentication mechanism, but it's currently missing support for encrypted cookies (haskell-servant/servant-auth#68). It would be great to see the knowledge contained in this library applied there. On the flip side, one thing servant-auth seems to be doing nicely with their SetCookie implementation is wrapping the response type with cookie headers from the auth primitive, so without relying on a separate Cookied combinator.

Thanks for reading!

@zohl
Copy link
Owner

zohl commented Nov 22, 2017

Hi,

I'm still not familiar with servant-auth codebase, but if it's possible to migrate to the same API they use, it will be very reasonable step towards the next release! I'll try to do it, so stay tuned!

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

2 participants