Test with application that uses traversal

[merwok]

Test with application that uses traversal

[hadrien]

Actually, pyramid_contextauth is context class based but we can easily implement inheritance based auth, can't we?

[merwok]

Yes, I think so :)

We may need to do something smarter than just isinstance, as we’ll want interfaces and subclasses to work, but the design of contextauth does not conflict with traversal.

[merwok]

Ah I remember now what problem I saw. In our apps that use dispatch, we define custom context factories in order to 1) delegate actual auth to them 2) access some stuff on the context instance, like facebook_data or order_info.

In a traversal-based app, we have resources as contexts, so we won’t be able to use context factories to parse the auth bits in the request.

I still think that having custom security contexts (distinct from resource contexts) is a good thing, we just need to find a way to attach them to the resource or request.

[hadrien]

Why won't we able to use context factories to parse the auth bits in the request?

[merwok]

Passing factory=SomeSecurityContext with route dispatch changes the root resource used for that view. With traversal, we’re not using routes and we’re not overriding the root resource for some views, because our contexts are resources.

[hadrien]

I still do not get it: We can register an authentication policy for a resource/context and run authentication for any request on the resource, right?

[merwok]

You’re right :)

[merwok]

My mistake was thinking that authz was done before traversal.