0005634: Enhance Documentation for 2FA (TOTP) - SOGo

ID	Project	Category	View Status	Date Submitted	Last Update

0005634	SOGo	Documentation	public	2022-10-31 13:12	2024-04-19 20:22

Reporter	Christian Mack	Assigned To	sebastien
Priority	normal	Severity	feature	Reproducibility	always
Status	acknowledged	Resolution	open

Summary	0005634: Enhance Documentation for 2FA (TOTP)
Description	In the SOGo Documentation should be a section about TOTP. Because that information is needed for account management. There are some informations lacking: How to disable 2FA when USER_A looses Key? Administrator with access to SOGo server has to use this command: /usr/sbin/sogo-tool user-preferences set defaults USER_A SOGoTOTPEnabled '{"SOGoTOTPEnabled": 0}' When 2FA was disabled and is reenabled again, will there be a new key generated? That key will be generated new when the user enables it again via webfrontend. When enabled via sogo-tool (???) When there is a centralised TOTP infrastructure, how can we set that TOTP key in SOGo? (???)
Tags	No tags attached.

sebastien 2022-11-01 09:20 administrator ~0016330	Thank you Christian for your feedback, I will update the documentation

bau@kg-fds.de 2024-04-19 20:22 reporter ~0017712	We already have an OTP infrastructure - our users are using Hardware-Token and/or google-autheticator-APP. So we have SharedSecrets which can be used. In Database sogo / Table sogo_user_profile there I found the Items "General":{"PrivateSalt":" (...) ","Salt":" (...) "}. How can one put the SharedSecret (Base32 or HEX - coded / SHA1 / 30s) into the database?

Date Modified	Username	Field	Change
2022-10-31 13:12	Christian Mack	New Issue
2022-11-01 09:20	sebastien	Note Added: 0016330
2022-11-01 09:21	sebastien	Assigned To	=> sebastien
2022-11-01 09:21	sebastien	Status	new => acknowledged
2024-04-19 20:22	bau@kg-fds.de	Note Added: 0017712