Service Accounts cannot be used in groups that require SAML authentication
The new Service Accounts feature is super neat! However, if you exist in a group that requires SAML authentication service accounts cannot be added to projects or subgroups.
It would be handy for service accounts to be able to bypass this restriction in some way, as it stands right now Service Accounts are pretty much inoperable for SAML restricted groups and require a robot users to be provisioned from your SAML provider and thereby taking up a full seat.
It is not possible to add the service account to a group with SSO enforced via the UI, the service account cannot be found. Doing so via API returns {"message":{"user":["is not linked to a SAML account"]}}
.
Edited by Daphne Kua