User authentication management

1. A method for registering a third-party website to utilize a multi-factor authentication service, comprising:

receiving of a valid digital identity certificate for the third-party website by the multi-factor authentication service;

receiving of an acquiescence to terms of use of the multi-factor authentication service for the third-party website by the multi-factor authentication service;

enabling the third-party website to utilize the multi-factor authentication service, in the absence of additional human intervention between the third-party website and the multi-factor authentication service before the third-party website initiates utilization of the multi-factor authentication service; and

utilizing a developer portal, the developer portal accessible by a developer of the third-party website and configured to:

provide an application programming interface (API) key to the developer of the third-party website, the API key configured to enable the third-party website to utilize the multi-factor authentication service;

provide a shared secret key to the developer of the third-party website, the shared secret key configured to authenticate a request to utilize the multi-factor authentication service; and

provide terms of use of the multi-factor authentication service to the third-party website, at least some of at least one of the receiving, the enabling, or the utilizing implemented at least in part via a processing unit.

2. A computer-readable storage device comprising computer-executable instructions, which when executed at least in part via a processing unit on a computer perform acts, comprising:

receiving, by a multi-factor authentication service, a digital identity certificate from a third-party website registering to utilize the multi-factor authentication service;

receiving, by the multi-factor authentication service, an acquiescence to terms of use by the third-party website for the third-party website to utilize the multi-factor authentication service;

enabling the third-party website to utilize the multi-factor authentication service, in the absence of additional human intervention between the third-party website and the multi-factor authentication service before the third-party website initiates utilization of the multi-factor authentication service; and

utilizing a developer portal, the developer portal accessible by a developer of the third-party website and configured to:

provide an application programming interface (API) key to the developer of the third-party website, the API key configured to enable the third-party web site to utilize the multi-factor authentication service;

provide a shared secret key to the developer of the third-party website, the shared secret key configured to authenticate a request to utilize the multi-factor authentication service; and

provide terms of use of the multi-factor authentication service to the third-party website.

3. The computer-readable storage device of claim 2 , comprising initializing the multi-factor authentication service by authenticating a mobile device of a user.

4. The computer-readable storage device of claim 3 , comprising providing a revocation mechanism to the third-party website, the revocation mechanism configured to unregister the authenticated mobile device from the multi-factor authentication service such that the mobile device is not authenticated.

5. The computer-readable storage device of claim 3 , the authenticating comprising at least one of:

displaying a first code for the user via the third-party website; or

sending a second code to the user via a message to the mobile device of the user.

6. The computer-readable storage device of claim 3 , the authenticating comprising at least one of:

receiving a first code from the user obtained via the third-party website; or

receiving a second code from the user obtained via a message from the mobile device of the user.

7. The computer-readable storage device of claim 6 , at least one of receiving the first code or receiving the second code comprising at least one of:

receiving an input via the third-party website; or receiving a mobile message comprising short message service (SMS).

8. The computer-readable storage device of claim 6 , at least one of the codes based at least in part on a locality of the user.

9. The computer-readable storage device of claim 2 , comprising providing a reporting mechanism to the third-party website, the reporting mechanism configured to provide a report comprising at least one of one or more transactions or user activity.

10. The computer-readable storage device of claim 2 , comprising alerting a user of an availability of the multi-factor authentication service based at least in part on a locality of the user.

11. The computer-readable storage device of claim 2 , comprising:

sending a user a test message prior to an initial use of the multi-factor authentication service; and

receiving a response to the test message from the user prior to the initial use of the multi-factor authentication service.

12. A system for enabling use of a multi-factor authentication service, comprising:

a first component configured to send a digital identity certificate of a third-party website registering to utilize the multi-factor authentication service to the multi-factor authentication service;

a second component configured to access a developer portal, the developer portal configured to:

receive an application programming interface (API) key based at least in part on the sent digital identity certificate, the API key for use by a developer of the third-party website, the API key configured to enable the third-party website to utilize the multi-factor authentication service, the developer portal accessible by the developer of the third-party website;

receive a shared secret key from the developer of the third-party website, the shared secret key configured to authenticate a request to utilize the multi-factor authentication service; and

receive terms of use of the multi-factor authentication service; and

a third component configured to send an acquiescence to the terms of use by the third-party website for the third-party website to utilize the multi-factor authentication service, the third-party website enabled to utilize the multi-factor authentication service in the absence of additional human intervention between the third-party website and the multi-factor authentication service before the third-party website initiates utilization of the multi-factor authentication service, at least some of at least one of the first component, the second component, or the third component implemented at least in part via a processing unit.

13. The system of claim 12 , the second component configured to initialize the multi-factor authentication service by registering a mobile device of a user with at least one of the third-party website or the multi-factor authentication service.

14. The system of claim 13 , the second component configured to provide a revocation user interface (UI) to the user, the revocation UI configured to allow the user to unregister the registered mobile device from the multi-factor authentication service such that the mobile device is not registered.

15. The system of claim 13 , the registering comprising at least one of:

displaying a first code for the user via the third-party website; or

sending a second code to the user via a message to the mobile device of the user.

16. The system of claim 15 , at least one of the codes based at least in part on a locality of the user.

17. The system of claim 12 , the second component configured to alert a user of an availability of the multi-factor authentication service based at least in part on a reverse internet protocol (IP) lookup.

18. The system of claim 12 , the second component configured to at least one of:

send a user a test message prior to an initial use of the multi-factor authentication service; or

receive a response to the test message from the user prior to the initial use of the multi-factor authentication service.

19. The system of claim 12 , the second component configured to provide a reporting user interface (UI) to a user, the reporting UI configured to provide the user with a report comprising at least one of one or more transactions or user activity.

20. The system of claim 19 , at least one of the transactions comprising at least one of a:

transaction date;

transaction time;

domain of a second third-party website initiating the multi-factor authentication service; or

internet protocol (IP) address of a second user engaging the multi-factor authentication service.