This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP JOTP Project"
Rob Upcraft (talk | contribs) |
Rob Upcraft (talk | contribs) m |
||
| Line 31: | Line 31: | ||
* OTP token generation, validation, and expiration. | * OTP token generation, validation, and expiration. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Project Leader == | == Project Leader == | ||
Robert Upcraft | Robert Upcraft | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| Line 59: | Line 49: | ||
== News and Events == | == News and Events == | ||
| − | |||
| − | |||
| Line 84: | Line 72: | ||
=FAQs= | =FAQs= | ||
| − | ; | + | ; Where can OWASP jOTP be downloaded? |
| − | : | + | : The source code, along with basic documentation, is located here: [https://github.com/upcrob/jOTP OWASP jOTP Repository] |
| − | |||
| − | |||
| − | : | ||
= Acknowledgements = | = Acknowledgements = | ||
==Volunteers== | ==Volunteers== | ||
| − | OWASP | + | OWASP jOTP is developed by a worldwide team of volunteers. The primary contributors to date have been: |
| − | * | + | * Rob Upcraft |
| − | |||
| − | |||
| − | |||
| − | |||
= Road Map and Getting Involved = | = Road Map and Getting Involved = | ||
As of [https://www.owasp.org/index.php/Projects/OWASP_JOTP_Project/Roadmap April 2014], the priorities are: | As of [https://www.owasp.org/index.php/Projects/OWASP_JOTP_Project/Roadmap April 2014], the priorities are: | ||
| − | Development work for jOTP is largely complete as of now. Because | + | Development work for jOTP is largely complete as of now. Because it is intended to be lightweight and focused on this use case, the feature set is not planned to grow significantly, if at all. Most future work will include bug fixes, and additional customization options developed on an as-needed basis. |
| − | Involvement in the development and promotion of OWASP | + | Involvement in the development and promotion of OWASP jOTP is actively encouraged! |
You do not have to be a security expert in order to contribute. | You do not have to be a security expert in order to contribute. | ||
Some of the ways you can help: | Some of the ways you can help: | ||
| − | * | + | * Submit issues to the GitHub repository. |
| − | * | + | * Submit pull requests for fixes to the GitHub repository. |
Revision as of 23:49, 10 April 2014
OWASP jOTPOWASP jOTP is a lightweight web application, implemented in Java as a small set of RESTful services, that can be used to generate, validate, and automatically expire one-time use password tokens. This tool could be useful in scenarios that require multi-factor authentication, but do not allow for more expensive / complex solutions that require physical tokens (magnetic id cards, RSA hard tokens, etc). Tokens generated may be sent either via email or SMS text message to end users. DescriptionA common use case for jOTP is as follows: 1. Client web application displays login page to user. 2. User enters username, password, and cell phone number. 3. Client application makes a call to jOTP, which subsequently generates a token and sends it to the user's cell phone. 4. The user receives the token, and enters it on the login page. 5. The client application contacts jOTP to validate the token. If the token was valid, along with the username/password (validated separately), the user is logged in. LicensingOWASP jOTP is available under the BSD 2-clause license.
|
What is JOTP?OWASP JOTP provides:
Project LeaderRobert Upcraft
|
Quick Download
Email ListNews and EventsClassifications
| ||||||||
- Where can OWASP jOTP be downloaded?
- The source code, along with basic documentation, is located here: OWASP jOTP Repository
Volunteers
OWASP jOTP is developed by a worldwide team of volunteers. The primary contributors to date have been:
- Rob Upcraft
As of April 2014, the priorities are:
Development work for jOTP is largely complete as of now. Because it is intended to be lightweight and focused on this use case, the feature set is not planned to grow significantly, if at all. Most future work will include bug fixes, and additional customization options developed on an as-needed basis.
Involvement in the development and promotion of OWASP jOTP is actively encouraged! You do not have to be a security expert in order to contribute.
Some of the ways you can help:
- Submit issues to the GitHub repository.
- Submit pull requests for fixes to the GitHub repository.
