[Repoze-dev] [issue159] repoze.what.plugins.sql bug with group permissions
Forest added the comment: Removing myself again. nlaurance, you don't have to keep adding me. If you'd really like to chat, we can use email. :) -- nosy: -forest __ Repoze Bugs <http://bugs.repoze.org/issue159> __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue159] repoze.what.plugins.sql bug with group permissions
Forest added the comment: I don't remember this bug, nor am I on the repoze.what dev team. Are you sure you meant to assign it to me? -- assignedto: forest -> nlaurance nosy: -forest __ Repoze Bugs <http://bugs.repoze.org/issue159> __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue77] repoze.who metadata plugin is called on every request
New submission from Forest : My testing shows that a meta-data provider plugin is called on every request. This is horribly inefficient for meta-data that is expensive to fetch, such as any that lives in a database. I would expect it to be fetched once when the user is authenticated, and then remembered using a cookie (or some other rememberer plugin). -- messages: 191 nosy: forest priority: bug status: unread title: repoze.who metadata plugin is called on every request __ Repoze Bugs <http://bugs.repoze.org/issue77> __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue76] repoze.who metadata plugin interface imposes an extra data fetch
New submission from Forest : I want to add meta-data to an authenticated user's environment, but I don't want to perform extra database operations to do it. Since the repoze.who spec only allows meta-data scribbling from within IMetadataProvider, and IMetadataProvider is separate from IAuthenticator, any meta-data that my authenticator already has must be thrown away, and then fetched again in a meta-data provider. This translates into an additional database fetch which could be avoided if the two interfaces were somehow integrated, or if IAuthenticator was allowed to provide meta-data. -- messages: 190 nosy: forest priority: bug status: unread title: repoze.who metadata plugin interface imposes an extra data fetch __ Repoze Bugs <http://bugs.repoze.org/issue76> __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue75] repoze.who should document logging.Logger support
New submission from Forest : PluggableAuthenticationMiddleware accepts a log_stream argument, which is documented as a stream-like object with a write() method. Looking at the code, I see that (thankfully) it accepts a logging.Logger object as well. This should be documented. -- messages: 188 nosy: forest priority: bug status: unread title: repoze.who should document logging.Logger support __ Repoze Bugs <http://bugs.repoze.org/issue75> __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue74] repoze.who form plugins have no obvious way to show "logged out" or "login failed" messages
New submission from Forest : The form plugins, which are the most obvious way to build a common web login page, have no obvious way to show "logged out" or "login failed" messages. Even with third party add-ons like formcookie, I end up having to perform three post-login-attempt redirects if I want to show a different "not logged in" message depending on whether the user is trying the first time, retrying, or has just logged out. If this was easier and had decent documentation, I'll bet more people would use repoze.who. -- messages: 187 nosy: forest priority: feature status: unread title: repoze.who form plugins have no obvious way to show "logged out" or "login failed" messages __ Repoze Bugs <http://bugs.repoze.org/issue74> __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue73] repoze.who IAuthenticator cannot report the reason for authentication failure
New submission from Forest : The interface defined for IAuthenticator doesn't allow it to report a reason for authentication failure. This prevents me from showing the user a sensible message when (for example) his login was refused due to excessive failed login attempts or a deactivated account. -- messages: 186 nosy: forest priority: feature status: unread title: repoze.who IAuthenticator cannot report the reason for authentication failure __ Repoze Bugs <http://bugs.repoze.org/issue73> __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
