Well, you could doe it the way you describe it, but I really have a problem
with that first parameter, I think this parameter has the wrong meening: I
meen why should a consumer know anything about the technical implementation
of your various authentication systems?
If your web service is an authentication service, then your Authenticate
method should have three parameters:
- username
- pasword
- security realm (or domain, if you want it to be Windows-like)
The security realm should be an enumeration, which would be used on the web
service side to instantiate the apropriate provider, through a factory for
example (see
http://www.dofactory.com/Patterns/PatternAbstract.aspx, if you'r
not familiar with it). Another solution would be to use the security
application block
(
http://msdn.microsoft.com/library/de...security1.asp).
based on datasource and in the run time ,I have to switch between data
identity providers like sql server,AD, oracle and even another
authentication webservice. Can somebody gives me a clue how to program
this?.Shall I store all data source in web.config and in run-time based on
the first paramter go through switch case statment or create classes and
interfaces for it .? I could n't find any samples that can give me some
idea.
Thankls for you time in advance.
Janathon
