Using comma as group separator is not conforming to standards/best-practices

[Corwitep]

SAML-multivalue-attributes are commonly encoded separated by semicolons rather than commas: "group1;group2;group3".

Please change the separator in UserData:getGroups() to a semicolon. Or better yet, make it a configurable option.

[h2o-commits]

A group field composed using spaces had previously worked without issues in the Nextcloud SAML app. Since the update (as of version 7.0.0 at the latest), these concatenated group fields with multiple groups no longer seem to work, and only individual groups are supported in SAML. Neither commas, semicolons, nor spaces appear to work as group separators in version 7.0.0. Can anyone confirm this?

[h2o-commits]

This does not work as group config value:

[blizzz]

A group field composed using spaces had previously worked without issues in the Nextcloud SAML app. Since the update (as of version 7.0.0 at the latest), these concatenated group fields with multiple groups no longer seem to work, and only individual groups are supported in SAML. Neither commas, semicolons, nor spaces appear to work as group separators in version 7.0.0. Can anyone confirm this?

Not aware of anything like this, and i expect it would break integration tests.

Anyway, please, instead of hijacking this feature request, please open a new bug report, and provide debug-level logs from a login attempt that fails to import groups.

[blizzz]

Please change the separator in UserData:getGroups() to a semicolon. Or better yet, make it a configurable option.

Can only be turned into a configurable options, otherwise would break all setups out there.