You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Todd James (JIRA)" <ji...@apache.org> on 2018/05/31 02:11:00 UTC

[jira] [Commented] (GUACAMOLE-96) Two factor authentication with Google Authenticator

    [ https://issues.apache.org/jira/browse/GUACAMOLE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495983#comment-16495983 ] 

Todd James commented on GUACAMOLE-96:
-------------------------------------

This seems to be working pretty well, but I'd love to see an additional property: a configurable property (say "totp-disable-enrollment") that allows the administrator to disable TOTP enrollment via Guacamole. Suppose a user is logging into an internet-exposed instance of Guacamole for the first time. They will be prompted to enroll in 2FA with TOTP. If the person that logged in is not the actual user (phished password, for example), they will still gain control of the Guacamole account. This almost defeats the purpose of 2FA for first-time users.

I would love to provide my users with an alternative TOTP enrollment method (which may tie into other systems, as well as modify the Guacamole database with the TOTP secret).

If such an option was to be set to false by the administrator, the user might be prompted with a custom message (as a second property, say "totp-disable-enrollment-message").

Any thoughts on this? Should I open a separate issue at this point? I'm willing to write the code myself, but I'd like to hear whether or not this would be a welcomed addition.

> Two factor authentication with Google Authenticator
> ---------------------------------------------------
>
>                 Key: GUACAMOLE-96
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-96
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: Documentation, guacamole-client
>            Reporter: L.J. van Ruiten
>            Assignee: Michael Jumper
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: guacamole-auth-totp-01-enroll-01-details-hidden.png, guacamole-auth-totp-01-enroll-02-details-shown.png, guacamole-auth-totp-01-enroll.png, guacamole-auth-totp-02-verify.png
>
>
> We have a few critical systems that are accessible through Guacamole and we have had some clients requesting a safer way to login. Two factor authentication is probably the best and easiest way to improve on the current username/password login, and I can imagine that this is something that other companies using Guacamole would also be interesting in this feature.
> I already did some tinkering myself and I found that Google Auhtenticator is simple to use, does not require any configuration (like you would with SMS codes) easy to implement and the "client" side of the authentication (the part that generates the codes) is easily integrated into existing apps.
> So far I have got Google Authenticator "kinda working". What I did is:
> - Started with guacamole-auth-jdbc as base
> - Added a secret key to a user account that is randomly generated upon creation. Also added a boolean field to indicate wether TFA is required for loggin in.
> - Used the GuacamoleInsufficientCredentialsException to redirect the user the a second screen asking for a TFA code after loggin in with the username and password.
> However as said before this only "kinda works" because:
> I have only gotten the TFA enable button to appear in the user's managing page, so it can only be enabled by administrators and that's also where I put the secret key shows up, so users can't find it themself.
> For as far as I could find the previous point cannot be done with just the guacamole-ext api. Even with the new API that enables you to insert HTML parts, you would also need an API endpoint to provide the secret key or ideally generate a QR code that Google Auhtenticator can read to bind a device to the account (I would like it to appear in the user's preference page). 
> So in summary if other people are interested I would be willing to contribute this, but I would need some directions and I have a few questions:
> - Am I right that it is currently not possible to add an API endpoint just using guacamole-ext to provide the QR codes?
> - What would be the way to implement this? Personally I thought that adding these options to the user's page would be the easiest.
> - Is this a feature you would like me to work on and contribute?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)