Re: [Auth]'non traditional' clients for DotGNU authentication?

[David Talbot]

dotgnu/passport systems can be broken into a few logical divisions:
1) A repository that stores a (username/password or other authentication 
scheme)
2) A repository that stores relevent information on that person
3) A way for clients to use the authentication in a generic way
   a) Concrete implementations in different languages and for different 
devices.

I suppose the overall rules you want for a system like this is to have 
the server behave the same in all situations and it's up to the client 
side implementers on what they want to do with that.

For example there was discussion a short time ago about biometrics. If 
I'm running a business and I want my people to login using a thumbprint, 
I could create a thumbprint to dotgnu gateway server that takes the 
biometric data that I've matched up with a dotgnu passport then passes 
the generic dotgnu password upstream to the dotgnu authentication 
server. The same could apply to a call center that uses voice print, etc 
etc.

The overall concept is you keep the server simple and let people build 
what they want in terms of client side applications and authentication 
gateways.

-David Talbot

David Oliver wrote:

> I'm new to this list, so pardon my ignorance.   Several digests ago, I saw
> a mini-debate about client-resident software (the need for, or not) and
> development browser selection.  Is this project considering non-PC clients?
> I'm thinking of wirelessly-connected PDAs, settop boxes, game consoles,
> etc..   Or, is the interest solely (or mostly) in traditional PCs running
> rich browsers?
>
> --
> David Oliver
> IBM Pervasive Computing
> address@hidden
>
>
> _______________________________________________
> Auth mailing list
> address@hidden
> http://dotgnu.org/mailman/listinfo/auth