On 19 Jan 2006, at 22:55, Wichert Akkerman wrote:
Currently adding roles through a RoleManager breaks ZODBRoleManager:
it reads a list of all roles when it created and assumes they do not
change after that. If you add a new role you can do that through
a RoleManager directly, but
On 23 Feb 2006, at 08:29, Wichert Akkerman wrote:
Hi,
Starting from 2.5 Plone will use PAS, and Plone 2.5-alpha2 is about to
hit the streets. For a release we would like to use released
versions of
all products used, which includes PluggableAuthService and
PluginRegistry.
The latest PAS
On 23 Feb 2006, at 12:16, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Hi,
Starting from 2.5 Plone will use PAS, and Plone 2.5-alpha2 is
about to
hit the streets. For a release we would like to use released
versions of
all products used,
On 1 Mar 2006, at 21:50, Tino Wildenhain wrote:
Jens Vagelpohl schrieb:
Zac has asked to step back a bit as the contact for the project and I
told him I could take over that part. That includes things like
release
stewardship.
One of the items that had been on my list for a while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9 May 2006, at 10:44, Emyr Thomas wrote:
Is there a way to use session auth instead of cookie auth with
PlonePAS as
I'd prefer not to use cookie auth for security reasons.
I notice PluggableAuthService has a Session Auth Helper plugin -
any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30 May 2006, at 08:56, Nicolas Rod wrote:
So my question: is there documentation anywhere with guidelines to
develop a PAS Plugin ? For instance, I'd like to know the order in
which the interface methods are called, where do the parameters
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Even though I am the perpetrator, I think the current way of caching,
using ZCacheable and RAM cache managers, is absolutely horrific. It's
cumbersome to set up and the ZCacheable API is ugly as sin using it
from code. I think simplification is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17 Aug 2006, at 10:36, Stephen Kenworthy wrote:
Hi all,
I've been trying out the Plone 2.5, Zope 2.8.7 release for the
first time and looking to migrate our intranet which is currently
Plone 2.1.
I love the new pas system but am still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Aug 2006, at 05:47, Serge Zagorac wrote:
Hi All
Is there any way or example how to configure plonePAS to consume a
web
service (in my case JAX-WS via SOAP ) in order to get user details?
This won't be a configuration issue, it will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30 Sep 2006, at 02:00, Rob Miller wrote:
hi,
i'm working on implementing the Plone member data as user
properties, but have hit a snag b/c PAS doesn't recognize images as
a possible property type. in the short term, does anyone object
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3 Oct 2006, at 05:40, Wichert Akkerman wrote:
I am updating my OpenId authentication plugin to be a standard python
package instead of a Zope product and am hitting a problem with
PluggableAuthService.all_meta_types: it filters the registered
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27 Nov 2006, at 18:00, Daniel Doerr wrote:
Hey guys,
recently I discovered a bug (or a feature???!!) in the way credentials
are stored in cookies with PluggableAuthService.
Daniel, please file this as a bug report in the PAS collector:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2 Feb 2007, at 19:45, Sidnei da Silva wrote:
Now, some might argue that this is an application-specific policy. The
fact is that there's no obvious way currently of 'vetoing' a login
based on the lack of certain user properties (like the email
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan, you just created a dependency on the CMF in the
PluggableAuthService, which has nothing to do with the CMF. There has
to be a better solution, otherwise the checkin must be reverted.
jens
On 25 Mar 2007, at 17:09, Stefan H. Holek
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3 Apr 2007, at 09:18, Wichert Akkerman wrote:
How do zope-pas@zope.org and [EMAIL PROTECTED] related to
each-other? I've always wondered that.
They're one and the same thing :) If they're not, we have a problem.
jens
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16 Apr 2007, at 13:56, robert rottermann wrote:
Hi there,
I have installed LDAPUserfolder 2.8beta and LDAPMultiPlugun for
Plone 2.5.0
Is there an easy way to list all users from a script.
something like we have in the ZMI user tab of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4 May 2007, at 05:17, Miles wrote:
Hi,
The interfaces definition from the plugins directory defines:
IRoleAssignerPlugin
def doAssignRoleToPrincipal( principal_id, role ):
However, it doesn't document any way to remove a role from a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5 May 2007, at 17:00, Wichert Akkerman wrote:
I think that a better approach would be to use events. I made a branch
a while ago which has an event which is fired when a new user is
created
which solves your use case perfectly. That branch is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6 May 2007, at 05:12, Miles wrote:
-1, we can not change semantics of existing interfaces.
I agree with this. Though the restriction is not documented
anywhere: I
am happy to add some explanatory notes though.
It does not need to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11 Jun 2007, at 00:22, Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
On 9 Jun 2007, at 20:28, Wichert Akkerman wrote:
I'm not quite happy with the current interfaces; I think it makes
more
sense to carry an IBasicUser instance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11 Jun 2007, at 15:14, Tres Seaver wrote:
Are there plans for a PAS 1.5 release? 1.4 is over 10 months old
now and
I would like to be able to include something newer in Plone 3.
If merging my z3-events branch is a factor in this I don't mind
FYI, the old PAS collector has been moved to Launchpad:
https://bugs.launchpad.net/zope-pas/
I have set up a team named zope-pas to receive bug requests etc,
however, I need everyone who still wants to be a collector supporter
to look at the team roster and let me know their Launchpad ID if
I have uploaded a new tarball to the same location.
jens
___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas
On Jan 30, 2008, at 14:01 , Mark Phillips wrote:
I looked at the bug reports and found 2 that relate to this error:
http://plone.org/products/remember/issues/44
http://plone.org/products/remember/issues/32
The suggested solution is to upgrade
PluggableAuthService to version 1.5.2, which I did.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 23, 2008, at 20:55 , Paul Winkler wrote:
(There does not seem to be a 1.6 branch.)
We have informally decided to proceed with a simpler trunk + tags
release policy, right now there's no need to add the complication of
release branches.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 24, 2008, at 18:11 , Paul Winkler wrote:
Any thoughts on the fix itself?
I've got two branches now, against trunk and against 1.5:
.../branches/slinkp-fix-anonymous-performance-branch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2009, at 07:40 , Ian McCracken wrote:
Recently upgraded from PAS 1.4 to 1.5.3 (and Zope 2.8.8 to 2.11.2).
I'm having a new problem with basic auth; namely, that basic auth
information is ignored when using wget. Browsers work fine, ZMI
27 matches
Mail list logo
