Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow more flexibility in SSO email domain filter #5011

Open
knolleary opened this issue Jan 14, 2025 · 0 comments
Open

Allow more flexibility in SSO email domain filter #5011

knolleary opened this issue Jan 14, 2025 · 0 comments
Labels
customer request requested by customer feature-request New feature or request that needs to be turned into Epic/Story details size:M - 3 Sizing estimation point
Milestone

Comments

@knolleary
Copy link
Member

Description

Currently, SSO is enabled for an entire email domain - such as @example.com. This is how the platform identifies if a user should use SSO or not.

We have a customer with multiple email domains representing different countries: @example.com, @example.it @example.pl @uk.example.com @example.co.uk etc.

Creating a separate SSO configuration for each of those domains is an administrative headache on both sides.

It would be helpful if the email domain filter for SSO configurations was more flexible. For example, supporting a wildcard glob - eg @example.*, or a comma-separated list of domains to match (or both...)

We would probably want to apply some strict rules as to what is supported - ie globs vs full regex.

https://app-eu1.hubspot.com/contacts/26586079/record/0-2/13089944531

Which customers would this be available to

Everyone - CE/Starter/Team/Enterprise

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

@knolleary knolleary added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do size:M - 3 Sizing estimation point customer request requested by customer labels Jan 14, 2025
@joepavitt joepavitt moved this to Todo in 🛠 Development Jan 15, 2025
@joepavitt joepavitt added this to the 2.14 milestone Jan 15, 2025
@joepavitt joepavitt removed the needs-triage Needs looking at to decide what to do label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer request requested by customer feature-request New feature or request that needs to be turned into Epic/Story details size:M - 3 Sizing estimation point
Projects
Status: Todo
Development

No branches or pull requests

2 participants