Josh Buker

The pr #200 addresses this, but is blocked by validation that the new CA is correct / safe.

The ideal resolution for the whole CA issue will be offloading that responsibility to Omniauth, imo. Assuming there are no issues switching to Omniauth, this will be fixed in v1.

@y-yagi Thanks Yagi, I'll get this into v1. Are there any other callbacks that you've found yourself wishing Sorcery provided?

I'm still working on getting the unload_plugin function to actually unload base rails callbacks such as `before_action` and `after_action`, but unloading a specific module is now possible, and worst case...

I've been considering removing the ORM Adapter abstraction and depending directly on the rails ORM methods, and this leads me to believe that might be the correct path. This would...

So it seems like the ORM adapter is mostly beneficial when it comes to defining the fields for MongoID, and handling before/after commit callbacks (which don't exist for Mongo, and...

@kevin-smartpatients Looks like a simple enough fix! Opening a PR would be appreciated. :smiley:

Presumably this is only an issue when testing locally, as you should always be using HTTPS in production. Still worth looking into and address though.

@sqlninja I'm about to look into this for Sorcery v1, one thing that I would like to know is if the community would prefer this to be a part of...

I created a new issue on the rework repo for discussing the JWT implementation, anyone who wants to help is welcome to comment there: Sorcery/sorcery-rework#9