4 ms·
Question: I work on a OSS CRM that historically relied on a CMS (Drupal/WordPress) for authentication. Now we're looking to make it more standalone, which mean
by mgbmtl 4y ago
Question: I work on a OSS CRM that historically relied on a CMS (Drupal/WordPress) for authentication.
Now we're looking to make it more standalone, which means coding our own login etc, and eventually things like SSO, LDAP, etc
Would this be a good fit?
If I understood the docs correctly, every install has to do their own setup, so it might not work? (some partners run it as a SaaS, but most run it as a PHP app on their own VPS).
- pseudopuppet 4y agoI think Logto will be good at “standalone identity service”, which means you can delegate all the sign-ins and user identity issues to Logto. (Just like SSO) So you can have only one Logto installed, and add multiple “API resources” (for apps with a dedicated API service) and “applications” (for traditional web apps or your native/spa clients) in Logto. No matter they are remote or local, VPS or SaaS. The logic is simple: - for clients and traditional web apps, when it detects user is not signed in, use SDK to redirect to Logto - for API services, add a middleware function to check if the request holds a valid token If you’d like to connect a third party identity provider, “connectors” will be your friend. These cases are covered in the docs. Hope my reply helps. Feel free to join our discord channel or send us an email if you have any questions. :-)
- mgbmtl 4y agoThanks for the detailed response. I'll mention it to our SaaS partners.