This is a generalization of my scenario: the user of a client app, when challenged for security, could choice to authenticate using more than one method, each one different as parameters (and backend systems to be called, in a more complex scenario).
for example:
- choice A using (id, pwd)
- choice B using (name, cellnum, token)
- choice C using (platenumber)
I'm thinking about a possible first solution where define different "submitAuthentication"-like backend procedures, each one with different signature, that the client calls based on the user's choice.
A possible second solution (really I don't like), to have a single "submitAuthentication"-like backend procedure where first parameters determines the kind of the choice, and following parameters will be mapped on the expected ones.
Is there some guidelines in order to realize that?
thanks.
