Support for Custom Authentication method

[infinitetrooper]

Provide support for users to add a custom auth method that doesn't follow OIDC or SAML protocols.

This will enable customers to adopt Appsmith and use business edition features such as GAC and Audit Logs while still maintaining the security protocols of their organization.

A-Force

Front conversations

[infinitetrooper]

User request on Front

[jmullins21]

Our team is also interested in this. We currently use Supabase to manage Auth for all of our tools and want to incorporate it a server level versus inside of public apps.

[infinitetrooper]

@jmullins21 - We're actively looking at this right now and want to understand your use case and how you'd like to use it with Appsmith. Can you please set up a short call with me at your convenience - https://calendly.com/akhil-appsmith/30min? Thank you.

[jmullins21]

@infinitetrooper I just set up a meeting for us.

[eedwardsSGS]

This is something we could use a solution for ourselves. We are considering moving to the paid edition of Appsmith but 1) we want some/many of our users to not even see the Appsmith back end / control panel, just log into our app 2) we want to use be able to use things like Supabase auth to control things.

In order to achieve this we need some kind of user type that can't see the back end and some way to handle auth between Supabase and Appsmith (such as logging in via Supabase auth and then passing that login to Appsmith to recognize the user).

And until we have this we need to just stick to a public app with our own login system.