You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Pierluigi Conti (Jira)" <ji...@apache.org> on 2020/07/06 08:48:00 UTC

[jira] [Commented] (GUACAMOLE-708) Allow database storage of arbitrary attributes for non-database users

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

Pierluigi Conti commented on GUACAMOLE-708:
-------------------------------------------

Hey there, after theese changes is there is not any possibilities to disable the TOTP checking procedure for a specific user, with previous version I was able doing that just removing the update parameter for the specified user.

Is there a way to reintroduce this? Something like if I specify a special value in the guac-totp-key-confirmed (something like DISABLED or so on).

 

Thanks
 

> Allow database storage of arbitrary attributes for non-database users
> ---------------------------------------------------------------------
>
>                 Key: GUACAMOLE-708
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-708
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: guacamole-auth-jdbc
>            Reporter: Nick Couchman
>            Assignee: Nick Couchman
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> A feature common to other applications that store data in one place and can authenticate from other sources is to enable automatic creation of user accounts within the database assuming the user is successfully authenticated elsewhere.
> I propose doing something similar with the Guacamole JDBC extension, or, depending on how the implementation works out, with the other extensions - a property that, disabled by default, could be enabled that would allow users authenticated successfully through other extensions to be automatically created within the JDBC extension.



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