Re:Launch HN: PropelAuth (YC W22) – End-to-end auth service ...
by aisrael on Wednesday March 16, 2022 @01:35PM
(#30701682)
Thanks! SAML and SCIM are both on our short-term roadmap and are really important. We want to implement it such that the code you write for supporting orgs today works regardless of the type of integration - and then the differences would primarily be the experience for your end-users.
There's a one to many mapping from users to organizations. We can also support users that don't have organizations. What types of configurations would you want?
Re:Launch HN: PropelAuth (YC W22) – End-to-end auth service ...
by ucarion on Wednesday March 16, 2022 @03:17PM
(#30702807)
Having the option for users to exclusively belong to organizations would be nice. It makes implementing tenant boundaries, and avoiding cross-account broken access control, much easier.
Re:Launch HN: PropelAuth (YC W22) – End-to-end auth service ...
by aisrael on Wednesday March 16, 2022 @03:46PM
(#30703141)
That makes sense, it definitely simplifies things. I like the idea of choosing between "everyone is signing up with their work accounts" and "users can join potentially multiple organizations, work related or otherwise". Thanks for the feedback!
1. SAML?
2. SCIM?
3. In your domain model, do users belong-to organizations? Or is it a has-and-belongs-to-many sort of deal? Can I configure that?