I spent some time discussing the idea of using IAM (Identity and Access Management) service providers like Auth0, OKTA, AWS IAM, with several of your team members (Derrick, Maxime, and Aurelien) in the context of a full-stack app where Strapi plays the backend role. Strapi being a generic CMS opens many new paths and I was very excited about this architecture. However, I made no impression on the three Strapi members who stated the using Passport.js as the basis for all subsequent AIM features implementation.
Assuming that I did not good enough "sales job", I decided to create a series of full-stack samples where the only constant is Strapi being used as the backend, while front ends and IM providers vary across most frameworks and PaaS providers. Having something real to show, might make my theory that Strapi is not just a toy tool, but could be used by Fortune 500 companies that all have very strict IAM requirements.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I spent some time discussing the idea of using IAM (Identity and Access Management) service providers like Auth0, OKTA, AWS IAM, with several of your team members (Derrick, Maxime, and Aurelien) in the context of a full-stack app where Strapi plays the backend role. Strapi being a generic CMS opens many new paths and I was very excited about this architecture. However, I made no impression on the three Strapi members who stated the using Passport.js as the basis for all subsequent AIM features implementation.
Assuming that I did not good enough "sales job", I decided to create a series of full-stack samples where the only constant is Strapi being used as the backend, while front ends and IM providers vary across most frameworks and PaaS providers. Having something real to show, might make my theory that Strapi is not just a toy tool, but could be used by Fortune 500 companies that all have very strict IAM requirements.