Hi everyone,

I'm about to attempt to check in some files related to security. 
Since no one had any objections to the architecture I proposed, I 
have basically a "no-op" skeleton for it: static client methods to set 
the principal and credential; role mapping that eliminates the 
indirection and uses the role as-is; no bean-to-bean context 
propagation; and authentication that just checks the password by 
making sure it is the same as the user name. We can add more 
realistic functionality next. (If there is a null principal, 
authentication/authorization is skipped. This is so people who want 
to can play with the security stuff, and people who don't can ignore 
it for now.)

I've never used CVS before, so I apologize in advance for all the 
chaos I'm about to cause. (I had to change a lot of key files, for 
things like propagation of security contexts...)

-Dan

Reply via email to