Ticket #57 (defect)
Opened 1 year ago
Last modified 10 months ago
Can't use authkit.authorize without authkit.authenticate
Status: reopened
| Reported by: | broder@mit.edu | Assigned to: | somebody |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | component1 | Version: | |
| Keywords: | Cc: | ||
If authkit.authenticate and authkit.authorize are going to be two separate middleware plugins, I should be able to use them independently. Currently authkit.authorize raises an Exception if the authentication middleware isn't present.
Attachments
Change History
11/09/08 18:50:16: Modified by thejimmyg
- status changed from new to closed.
- resolution set to wontfix.
11/23/08 16:45:05: Modified by broder@mit.edu
- status changed from closed to reopened.
- resolution deleted.
My particular use case is that I'm using Apache to provide the authentication mechanism. It sets the REMOTE_USER variable, so I don't need AuthKit? to provide authentication, but I do want to use it to check the authorization of the user.
The authentication and authorization middleware both use the same setup.enable option so the authorization middleware needs access to the authentication middleware's configuration. All the authorization adaptors use the same config option too. It would be easy enough to change them all to use a different option so that the two could be de-coupled but I can't think of a reason why you'd want the authorization middleware on its own. Can you provide a suitable use case and I might be able to come up with a more effective solution?
Cheers,
James