JaCarta U2F

JaCarta U2F - Universal USB token, intended for use as a second factor in the password authentication of end-users of online services that support the FIDO U2F standard.

• "Cloud" services (Dropbox, Google Cloud Platform)
• Postal services (GMail)
• File hosting, video hosting, hosting of IT projects and their joint development (Google Drive, YouTube, GitHub)
• Electronic payment systems (Google Wallet)
• Social networks (Google+)

Solved problems:

• Enhance password authentication of users when accessing Web resources by switching to two-factor authentication using a token
• Eliminate users from having to remember complex passwords. By using the second authentication factor, the password complexity requirements can be significantly reduced
• Use one device to access different resources

Functionality of JaCarta U2F: FIDO U2F authentication Key features of JaCarta U2F: Token JaCarta U2F Has a number of features that distinguish it from tokens using alternative authentication technologies.

• Self-registration of users - unlike authentication systems based on traditional PKI tokens, the registration of the JaCarta U2F token on a particular Web resource does not require the participation of an administrator. To register, you just need to enter your login and password, connect the token to the computer and click on the button (thereby confirming the user's physical presence at the computer). When a user logs his U2F token on a Web resource, the key pair (public and private key) is generated without a public key certificate. The generated key pair is used for further authentication.
• The one-to-many concept - One token can be used to access a variety of different Web resources (the amount of resources is limited only by the amount of storage of the token used to store the authentication data).
• Phishing Protection - each private key stored in the token's memory and used to access a particular resource is "linked" to the address of the given resource (URL). Thus, if an attacker tries to redirect a user to a "fake" resource, the user will not be able to authenticate, because the private key corresponding to the "fake" resource will not be found.