Typical usage scenarios

You should consider Passport authentication when:

·       Your site will be used in conjunction with other Passport-enabled sites and you want to give single-sign-on capability to users accessing these sites.

·       You do not want to maintain a user name and password database.

You should not consider Passport authentication when:

·       You want to exploit usernames and passwords already stored in your own database or Active Directory. (Although, with additional code, you can potentially map a Passport ID to a user account.)

·       Your clients are other computers that access the site programmatically.