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

Nick Couchman commented on GUACAMOLE-1333:
------------------------------------------

[~dpt48]:

{quote}
Because we're very interested by the Radius Group option, we're thinking about 
hiring a dev to modify/adapt the current one and reverse code to the project.
{quote}

You're certainly welcome to do that, and if you're able to contribute the code 
back to the project, that would be much appreciated. Just be aware that the 
contribution has to be in line with the overall project guidelines:

http://guacamole.apache.org/open-source/

{quote}
Do you have any comments to or are you ok with that ?
{quote}

Sure, but that should be tracked under the current issue for that, 
GUACAMOLE-792.

> Force second auth
> -----------------
>
>                 Key: GUACAMOLE-1333
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1333
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-auth-jdbc-mysql, guacamole-auth-ldap, 
> guacamole-auth-radius
>    Affects Versions: 1.3.0
>            Reporter: Nicolas Baudrand
>            Priority: Minor
>
> Hi !
> We're using Guacamole Auth ldap and then map returned groups with existing 
> mysql groups to assign profiles.
> Now, we want to ask for TOTP to our central server that is reachable by 
> radius.
> So, I have enabled auth-jdbc, auth-ldap and auth-radius
> With username+pass (ldap), I access to my AD group profile.
> With username+otp or username+pass+otp (radius), I have an empty profile 
> because no groups are returned by radius.
> Is it possible to force a second auth after LDAP (returning 
> GuacamoleInsufficientCredentialsException) so that we can ask for OTP after 
> LDAP.
> Guacamole TOTP is great but not centralized and I don't want to ask my users 
> to register a new Token for each application.
>  
> Thanks a lot for this great product
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to