Role-based access synchronized with 3rd-party authentication
acknowledged
Rob Newman
Merged in a post:
Automatically add users to organization
C
Combined Scallop
We are currently using Azure SSO for authentication. Is it possible to have users automatically added to our Organization when they first log in? Users currently need to be manually added to the Organization via the "participants" page.
Rob Newman
Merged in a post:
SSO authentication and checking for existing users
K
Kumquat Possum
Support the ability to dynamically add and remove users from a Seqera Platform instance without needing to modify any configuration settings and redeploy.
Rob Newman
acknowledged
Rob Newman
Merged in a post:
Delegate group management to OIDC provider
B
Big Parrot
We'd like the ability to sync group membership (power users, admins, regular users) from OIDC which comes from Okta, instead of having to mange those manually within the Seqera Platform
Rob Newman
Merged in a post:
LDAP authentication
P
Peaceful Clownfish
We had an open feature request regarding LDAP authentication for the Tower Enterprise, which would remove the annoying need of providing an email every time to log in.
Do you know what would be the timeline for this feature?
Rob Newman
Merged in a post:
Admin panel: sync teams via OIDC LDAP groups
B
Brass Wildcat
Introduce an automated mechanism to import and keep up-to-date user-team associations directly from the organization's LDAP/OIDC system. This enhancement would streamline user management by aligning users with the corresponding groups they can access in the organization system. This could simplify permissions management and help ensure consistency between the Seqera Platform and the organization's existing LDAP/OIDC structure.
This would reduce the manual effort in managing permissions, providing a more robust and synchronized experience for administrators and end-users.
Rob Newman
Merged in a post:
Role-based Access Control using existing Active Directory groups
A
Alive Panda
Currently, there is no way to translate Seqera Platform's user's permissions into file system permissions.
The workaround is that customers are creating shares for each one of their workspaces. They have a share mounted in the HPC environment and the user's PC for each workspace. Each share is assigned an AD group. Whenever a user needs access to launch and retrieve data from a pipeline, the administrator has to manually add them to Seqera Platform and then to the AD group, which is inefficient.
Having restrictions on who can access each share based on Active Directory groups (which are also replicated in the Azure AD service) would be much more efficient: creating/assigning groups from LDAP or Azure AD to workspaces so that administration would be easier and not duplicated.