I think your reasoning is sound...!
Scott
Luke Taylor wrote:
I agree that reusability is important but I'm not convinced that these
changes are justified on this basis, or that is just about balancing
reusability and ease of use. The use of constructor arguments is about
guaranteeing that
I have been asked to write a webservice in java that when given a username/password will return a security token to a .net client so that .net can then use it for future calls to java Webservices and acegisecurity will kick in. I know that this doesnt sound desirable, but should it be
Check out CAS. It may be what you are looking for.
-Matt
On 7/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I have been asked to write a webservice in java that when given a
username/password will return a security token to a .net client so that .net
can then use it for future calls to
By using xFire, CAS supports remoting its protocol, which can help in
this situation (we actually use it at Rutgers to authenticate
services). CAS also supports remoting its protocol via any of the
remoting options Spring supports.
I'm not sure how your application/web services are set up,
