Service level authorization for users

[jbittel]

Service level authorization for users

[jbittel]

The philosophy of MamaCAS, and CAS in general, is that the server deals with authentication of the user and does not handle authorization. Ideally, you have at least some control over the behavior of the configured services, and each is responsible for determining what the user can do once authenticated. This appears to match your first example, where each service would check the returned attributes to see if it is authorized for that particular user and abort the login at that point if it is not.

I also just pushed a commit that might be of help in this scenario. It causes the the service URL to be passed to each callback, making it available for customizing the returned attributes. If this provides enough information for you to implement the checks and/or return the information you need, that would allow you to implement your authorization checks outside of MamaCAS and obviate the need to maintain a fork.

Does that help meet your needs?

[k0nG]

Yeah that makes sense to me. Using attributes to send any information the client service will need to check authorization.

Thanks for your changes in commit: cc54e12#diff-0

Are they on pypi now? Thanks for your speedy reply and help. Its great not having to fork this off for our own needs.

[jbittel]

No, this change isn't released yet. I'm planning to do an official 1.0.0 release in a few weeks, so it will be included in that.

Thanks!