mirror of
https://github.com/go-gitea/gitea
synced 2024-12-21 06:54:14 +01:00
d77176912b
* Migrate to go modules * make vendor * Update mvdan.cc/xurls * make vendor * Update code.gitea.io/git * make fmt-check * Update github.com/go-sql-driver/mysql * make vendor
60 lines
3.5 KiB
Markdown
60 lines
3.5 KiB
Markdown
# otp: One Time Password utilities Go / Golang
|
|
|
|
[](https://godoc.org/github.com/pquerna/otp) [](https://travis-ci.org/pquerna/otp)
|
|
|
|
# Why One Time Passwords?
|
|
|
|
One Time Passwords (OTPs) are an mechanism to improve security over passwords alone. When a Time-based OTP (TOTP) is stored on a user's phone, and combined with something the user knows (Password), you have an easy on-ramp to [Multi-factor authentication](http://en.wikipedia.org/wiki/Multi-factor_authentication) without adding a dependency on a SMS provider. This Password and TOTP combination is used by many popular websites including Google, Github, Facebook, Salesforce and many others.
|
|
|
|
The `otp` library enables you to easily add TOTPs to your own application, increasing your user's security against mass-password breaches and malware.
|
|
|
|
Because TOTP is standardized and widely deployed, there are many [mobile clients and software implementations](http://en.wikipedia.org/wiki/Time-based_One-time_Password_Algorithm#Client_implementations).
|
|
|
|
## `otp` Supports:
|
|
|
|
* Generating QR Code images for easy user enrollment.
|
|
* Time-based One-time Password Algorithm (TOTP) (RFC 6238): Time based OTP, the most commonly used method.
|
|
* HMAC-based One-time Password Algorithm (HOTP) (RFC 4226): Counter based OTP, which TOTP is based upon.
|
|
* Generation and Validation of codes for either algorithm.
|
|
|
|
## Implementing TOTP in your application:
|
|
|
|
### User Enrollment
|
|
|
|
For an example of a working enrollment work flow, [Github has documented theirs](https://help.github.com/articles/configuring-two-factor-authentication-via-a-totp-mobile-app/
|
|
), but the basics are:
|
|
|
|
1. Generate new TOTP Key for a User. `key,_ := totp.Generate(...)`.
|
|
1. Display the Key's Secret and QR-Code for the User. `key.Secret()` and `key.Image(...)`.
|
|
1. Test that the user can successfully use their TOTP. `totp.Validate(...)`.
|
|
1. Store TOTP Secret for the User in your backend. `key.Secret()`
|
|
1. Provide the user with "recovery codes". (See Recovery Codes bellow)
|
|
|
|
### Code Generation
|
|
|
|
* In either TOTP or HOTP cases, use the `GenerateCode` function and a counter or
|
|
`time.Time` struct to generate a valid code compatible with most implementations.
|
|
* For uncommon or custom settings, or to catch unlikely errors, use `GenerateCodeCustom`
|
|
in either module.
|
|
|
|
### Validation
|
|
|
|
1. Prompt and validate User's password as normal.
|
|
1. If the user has TOTP enabled, prompt for TOTP passcode.
|
|
1. Retrieve the User's TOTP Secret from your backend.
|
|
1. Validate the user's passcode. `totp.Validate(...)`
|
|
|
|
|
|
### Recovery Codes
|
|
|
|
When a user loses access to their TOTP device, they would no longer have access to their account. Because TOTPs are often configured on mobile devices that can be lost, stolen or damaged, this is a common problem. For this reason many providers give their users "backup codes" or "recovery codes". These are a set of one time use codes that can be used instead of the TOTP. These can simply be randomly generated strings that you store in your backend. [Github's documentation provides an overview of the user experience](
|
|
https://help.github.com/articles/downloading-your-two-factor-authentication-recovery-codes/).
|
|
|
|
|
|
## Improvements, bugs, adding feature, etc:
|
|
|
|
Please [open issues in Github](https://github.com/pquerna/otp/issues) for ideas, bugs, and general thoughts. Pull requests are of course preferred :)
|
|
|
|
## License
|
|
|
|
`otp` is licensed under the [Apache License, Version 2.0](./LICENSE)
|