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
For some sites, opting into authentication for every route might not be the most ideal. In order to remove this functionality, you have to configure the bottle in a way that might not be the most intuitive:
Import<ApplyAuthentication>(authentication =>{authentication.Include(chain =>false);//Configure routes to include authentication});
It would be nice to have an option to easily opt out of authentication from all routes and then configure the routes that need to be authenticated.
The text was updated successfully, but these errors were encountered:
For some reason, this little configuration above doesn't work for me - it still tries to authenticate every route unless I add the NotAuthenticated attribute on every class. You say it is doable today Josh - but how?
The way that the configuration aspect of FubuMVC.Authentication is right now is flawed and non-functional (the Utah guys stumbled into it). I'm actually working on that very thing this morning so that my team and our other Utah teams can start using that Bottle.
Give me a couple hours and I'll have an update for the list. The signature is going to change though.
On Nov 29, 2012, at 3:37 AM, Robert Greyling [email protected] wrote:
For some reason, this little configuration above doesn't work for me - it still tries to authenticate every route unless I add the NotAuthenticated attribute on every class. You say it is doable today Josh - but how?
—
Reply to this email directly or view it on GitHub.
For some sites, opting into authentication for every route might not be the most ideal. In order to remove this functionality, you have to configure the bottle in a way that might not be the most intuitive:
It would be nice to have an option to easily opt out of authentication from all routes and then configure the routes that need to be authenticated.
The text was updated successfully, but these errors were encountered: