Storing the credentials on a YubiKey NEO ensures that your credentials are safe, even if your phone is compromised.
It also makes it easy to move between multiple Android devices.
The use of this app requires a YubiKey NEO with the ykneo-oath applet installed.
Instructions for installing the applet can be found here: http://forum.yubico.com/viewtopic.php?f=26&t=1159
NOTE: This app was previously known as YubiOATH. The name has been changed to Yubico Authenticator.
The functionality of this app has been superseded by the YubiOATH app: https://play.google.com/store/apps/details?id=com.yubico.yubioath
The new app allows multiple OATH secrets to be stored and does not require the use of the YubiKeys slots. Note that the new app does require the installation of an applet on the YubiKey NEO device itself. Instructions on how to do so can be found in the description of the YubiOATH app.
This helper App allows you to generate OATH TOTP codes with the secret [or seed] stored in a YubiKey NEO's secure element. Using this App, you can use 2-step verification with services such as Google Apps/Gmail or DropBox without having the 2nd steps' secret stored on your Android device - this is a concern to many who are using the same device to access the service.
This App is community supported, and there is a forum thread at http://forum.yubico.com
Source code and issue tracker for this app is available at https://github.com/Yubico/yubitotp-android
Once installed the app does not need to be started. Just swiping the YubiKey NEO against the phones NFC reader will cause it to run, displaying a message to indicate that the OTP has been copied, all without leaving the currently running app.
Note that the default NDEF programming needs to be used. If you've reprogrammed the NDEF tag of your YubiKey NEO, you will need to change it back to the URL: https://my.yubico.com/neo/
This can be done using the personalization tool: http://opensource.yubico.com/yubikey-personalization-gui/
When using a YubiKey NEO with a static password in scan code mode you will need to configure which keyboard layout to use in the YubiClip Settings. Currently only the US layout is supported. If you would like to see additional layout support, please consider contributing code via a pull request to our source code repositiory: https://github.com/Yubico/yubiclip-android/
Pledge supports multiple tokens (Pledge profiles), customer branding, protection with PIN codes, easy-to-use copy and paste function for the OTP, self-enrollment of tokens (Pledge profile) and many more functions.
To start using Pledge, contact your service provider or system administrator to get instructions how to enroll your device.
Pledge is a part of McAfee One Time Password.
Easy input by Hand Writing
*Keyboard on the screen!
Easy input by your familiar keyboard
Screen is divided half and your words will turn around and be colored differently to be shown to the other for easy recognition.
Android 3.0 and above, Screen size 7 inch and above
“IfTalk Deluxe” with new features will be available soon.
A PINgrid token must be registered with a user account on the server (e.g. Winfrasoft AuthCentral) and the user will only be able to login if they know their pattern and physically have their phone with them. Unlike traditional 2FA solutions, only the person who knows the pattern can actually use the token as they are used together to login and the pattern is never revealed to anybody.
- 2 Factor Authentication soft token
- Transaction Signing / Verification
- Supports multiple web sites & systems
- Get a new One Time Code every 60 seconds
- Patent pending security algorithm
- Based on OATH with FIPS compliant cryptography
PINgrid is an easy to use and highly secure authentication solution for the 21st century.
[AuthCentral, PINgrid, PINphrase, PINpass, 2FA, Token, OATH, RSA, GrIDsure, SafeNet, Authentication, Fob, OTP, OTC, PIN, Code, Password]
FreeOTP is open source and free software! Licensed under the Apache 2.0 license, you can obtain the source code for FreeOTP at https://fedorahosted.org/freeotp for review or modification. Contributions are welcome!
FreeOTP implements open standards! This means that no proprietary server-side component is necessary: use any server-side component that implements these standards. We personally recommend FreeIPA (http://www.freeipa.org), which uses TOTP. However, any standards-compliant implementation will work. Currently, FreeOTP provides implementations of HOTP (RFC 4226) and TOTP (RFC 6238).
- Aumenta a segurança no relacionamento de clientes com a organização;
- Maximiza o uso de tecnologias como o telefone celular;
- Facilita a percepção do usuário em relação a ameaças que estejam em curso;
- Coíbe as fraudes ocasionadas pelo acesso indevido a senhas, entre outras;
- Reduz os investimentos, dispensando a aquisição de dispositivos de autenticação tradicionais;
- Método de sincronismo que diminui a dependência com central de atendimento.