[
https://issues.apache.org/jira/browse/GUACAMOLE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710134#comment-17710134
]
Nick Couchman commented on GUACAMOLE-1766:
------------------------------------------
[~ro-kei]: In order for your SAML account to have admin privileges, you need to
create either a user or group in the JDBC module that has admin privileges,
where the user or group name matches (including case sensitivity) the one
you're logging with via SAML. So if you're logging in via SAML with a user that
has username "Account1", you'll need to have that account present in the JDBC
module and granted access.
Please read this section in the manual - it talks about LDAP + JDBC, but the
principle applies to anything with JDBC:
https://guacamole.apache.org/doc/gug/ldap-auth.html#associating-ldap-with-a-database
Also, the issue you're facing is probably not a bug, so please subscribe to the
mailing list and ask questions, there, first:
https://guacamole.apache.org/support/
> Administrator screen does not appear when SAML is used
> ------------------------------------------------------
>
> Key: GUACAMOLE-1766
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1766
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-saml
> Affects Versions: 1.5.0
> Environment: Ubuntu20.04.6LTS
> apt Apache2
> apt tomcat9
> Reporter: ro-kei
> Priority: Major
>
> When a procedure that worked fine with Guacamole 1.4.0+SSO-SAML is
> implemented with 1.5.0+SSO-SAML, authentication passes but the admin menu
> does not appear, even for users who have been granted admin rights.
> When I used the same SQL with JDBC authentication using MySQL only, the admin
> menu was displayed without any problem.
> I thought it might be a client problem, but even with
> Server1.5.0+Client1.4.0, the admin menu did not appear.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
