Page MenuHomekolab.org

Multiple TOTP configurations with the same label but different secrets
Open, NormalPublic

Description

After multiple tries to configure a FreeOTP mobile device application, the following occurs in the database;

{s:14:\"kolab_2fa_blob\";a:7:{s:29:\"totp:5fc162945e003b99ed1802e4\";a:3:{s:5:\"label\";s:17:\"Mobile App (TOTP)\";s:7:\"created\";i:1436182181;s:6:\"secret\";s:16:
\"VRBLJ36GP2DQU52U\";}s:29:\"totp:a8f2b8175b564914b05beaa7\";a:3:{s:5:\"label\";s:17:\"Mobile App (TOTP)\";s:7:\"created\";i:1436182411;s:6:\"secret\";s:16:\"DTMYJ2EN2GZELG2I
\";}s:29:\"totp:67dd69bc6c3d51759d454436\";a:3:{s:5:\"label\";s:17:\"Mobile App (TOTP)\";s:7:\"created\";i:1436182825;s:6:\"secret\";s:16:\"7PKD5ZSCSWL5TKTP\";}s:29:
\"totp:fffd1c196c9c3ff10550de44\";a:3:{s:5:\"label\";s:17:\"Mobile App (TOTP)\";s:7:\"created\";i:1436184882;s:6:\"secret\";s:16:\"KC3WN2RE54WXWMUP\";}s:29:
\"totp:d99205f07d794a0126cf636d\";a:3:{s:5:\"label\";s:17:\"Mobile App (TOTP)\";s:7:\"created\";i:1436185227;s:6:\"secret\";s:16:\"UQKOUS7GZSANT2MS\";}s:29:
\"totp:fa72af71a64266e8f01ab6ac\";a:3:{s:5:\"label\";s:17:\"Mobile App (TOTP)\";s:7:\"created\";i:1436185506;s:6:\"secret\";s:16:\"5VHUEOSJDROJGNAG\";}s:29:
\"totp:676dd53f7b56e1958fe426a3\";a:3:{s:5:\"label\";s:17:\"Mobile App (TOTP)\";s:7:\"created\";i:1436186676;s:6:\"secret\";s:16:\"NECQDAILCUDFNDJG\";}}

It is unclear which of the tokens is being used for the attempt to validate the configuration of the mobile device application.

Details

Ticket Type
Task

Event Timeline

vanmeeuwen updated the task description. (Show Details)
vanmeeuwen raised the priority of this task from to 60.
vanmeeuwen changed Ticket Type from Task to Task.
vanmeeuwen added subscribers: bruederli, grote, vanmeeuwen.

None of them is used. Only factors with an "active" property are considered during the authentication process. The others are temporarily stored tokens needed to display the configuration step. Once one is actually confirmed and activated, all other temporary entries will be removed.

vanmeeuwen lowered the priority of this task from 60 to Normal.Mar 28 2019, 8:13 AM