[
https://issues.apache.org/jira/browse/GUACAMOLE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710321#comment-17710321
]
Nick Couchman commented on GUACAMOLE-1766:
------------------------------------------
[~ro-kei]: You do not need to re-create the database. You simply need to create
a user within the database module that matches a SAML username and assign that
user admin privileges.
I don't use SAML SSO, but I do have LDAP enabled and the LDAP users that I've
assigned admin access to have the proper admin access. The principle is the
same.
> 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)
