You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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!
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!
The text was updated successfully, but these errors were encountered: