#Logging out of an App

1 messages · Page 1 of 1 (latest)

proud wasp
#

Is there a way of just doing a call like appsmith.app,logout so that I can log out from the appsmith instance?

cunning pumiceBOT
#

Hello! I'm AppsmithBot, here to assist you with your Appsmith queries.

To log out from an Appsmith instance, you can use the logout option available in the user profile menu. Simply click on your profile icon in the top-right corner of the Appsmith interface, and you should see an option to log out?5:1?discord-support-1.json?.

If you are looking for a programmatic way to log out, Appsmith does not currently provide a direct API call like appsmith.app.logout for logging out. You would need to handle session management and token revocation through your authentication provider if you are using custom authentication?5:13?Appsmith Documentation.pdf?.

If you don't find my response helpful, you can request to speak to a human agent.

proud wasp
#

i have to be honest that I am finding the whole authentication process somewhat confusing. It appears that I can create users and assign them roles within the appsmith isntance that I have running on a Digital Ocean Droplet. Users log in to appsmith. THEN the app appears on the screen.
What happens then? I am using a Supabase database for my app and I want to use RLS on that database. This means that users have to log into my app - so now it appears there are two levels of login - one just to get into Appsmith, and then one to actually log into my app. Iv'e seen some good tutorials about RLS by Confidence on your channel, but I am still not clear as to how to get to the point where users go to a website, and just do one login which allows RLS to work on the backened database.

#

Any help would be appreciated. I am trying to figure out how to set up the login process for users, and I can't release the app to my colleagues until this is clear. Thank you.

cunning pumiceBOT
#

To achieve a single login experience for both Appsmith and your Supabase database with Row Level Security (RLS), you can consider implementing a custom authentication flow. Here's a general approach:

  1. Custom Authentication: Use a custom authentication method that integrates both Appsmith and Supabase. This involves setting up an authentication provider that both systems can use. You can use OAuth, JWT, or any other token-based authentication system that Supabase supports.

  2. Single Sign-On (SSO): Configure Single Sign-On (SSO) in Appsmith. This allows users to log in once and access both Appsmith and your application seamlessly. Appsmith supports SSO through SAML, OpenID Connect, and OAuth?9:11?Appsmith Documentation.pdf?.

  3. Supabase Authentication: Use Supabase's authentication features to manage user sessions and RLS. Supabase provides a built-in authentication system that can be used to manage user access and roles?10:12?Appsmith Documentation.md?.

  4. Role Management: In Appsmith, you can manage user roles and permissions through the Admin Settings. This allows you to define what each user can access within your Appsmith instance?9:13?Appsmith Documentation.pdf?.

  5. Programmatic Access Control: Use Appsmith's programmatic access control to manage access to various entities such as widgets, datasources, APIs, and queries based on user roles?9:13?Appsmith Documentation.pdf?.

By setting up a custom authentication flow and leveraging SSO, you can streamline the login process for your users, allowing them to authenticate once and access both Appsmith and your Supabase-backed application. This setup will also enable you to enforce RLS on your Supabase database effectively.

If you don't find my response helpful, you can request to speak to a human agent.

proud wasp
#

That is helpful, but I would appreciate more guidance