On Fri, May 30, 2025 at 4:47 AM Peter Camps <[email protected]> wrote:
> Hi, > > > > Finally figured it out (sort of). > > > > I created a group in Azure AD with the same name as the connections-group > in Guacamole. After that I created a group claim in the configured SAML > based SSO. > > Selected “Security Groups” and used the Group ID attribute, choose > “Customize the name of the group claim” and gave it the name “groups”. > > > > This did not work until I renamed the connections-group in Guacamole with > the Group-ID of the Azure group. So instead of using a common displayname I > had to use the Group-ID. > > > > If there is anybody who knows how I can use the displayname of the group > instead of the Group-ID, please let me know. > > > Hi, Peter, I have another application - NextCloud - where I use Azure SAML SSO, including the groups, and this is the configuration I have for the Groups claim for that, which results in the human-readable name being sent through in the SAML claim. Not sure if this will help or not. I have not tried this with Guacamole, yet, so not sure if it works the same, there. [image: image.png] [image: image.png] -Nick >
