serac/cas — comment on commit 30e2882469647e5e6cb44e1f33f574b8c8dcf5bd
File:  line 0
By serac:

Good question. The difficulty is that security for this kind of resource will vary wildly by security policies of deployers. I would imagine we're one extreme where it will likely be wide open; I can also imagine that others will want some kind of credential to access it. In any case I think we can accommodate most if not all needs with Spring Security, which is used at present for securing the services management console. I'm inclined to configure the default authorization as an IP subnet filter restricted to localhost. It would be trivial to replace localhost with a deployer-specific subnet, plug in another authorization model, or remove it entirely.