Re: more than one table to check user

andi wrote:

> the question i was working for the last two days is to identify a user 
> against more than one table. i can imagine, that it will be possible 
> very easy, but i was just too stupid to see the solution. my aim is to 
> identify a user via its email and a unique tan, which is not located in 
> the usertable. i tried something like that, but if i define a field for 
> password that is not in the usertable, it won't work. also the field 
> 'tan' (located at the bottom) is not requested by default, although it 
> is set to required... ?

The default client container does not support it. You would have to 
extend the given container and modify the _readUserData() method.

regards,
Lukas