zlacker

[parent] [thread] 2 comments
1. somege+(OP)[view] [source] 2023-04-11 17:24:20
I think your positioning is wrong. The problem this solves is auditing user accounts in SaaS applications. That is a great problem to be solving, and you can position yourself on that! Why talk about 'SSO Tax' when this has nothing to do with SSO?

There is at least one other 'open' library for solving this problem (https://github.com/ConductorOne/baton).

However, I like how you're scraping web data for apps that don't have APIs. I've been waiting for someone to do that. That said, I want it built into other tooling I have purchased, so I don't have to implement myself.

replies(2): >>PhLR+54 >>daniel+ah
2. PhLR+54[view] [source] 2023-04-11 17:41:42
>>somege+(OP)
'Auditing user accounts in SaaS applications' is a pretty good summary of what the current version is about. The 'SSO-Tax' has become a synonym for the extra charges of SaaS vendors in which they usually bundle 3rd party SSO, SCIM and SAML.

What other tooling would you want it to integrate with?

3. daniel+ah[view] [source] 2023-04-11 18:34:04
>>somege+(OP)
Cerby does this. I'm not them, but I know one of the guys there.
[go to top]