Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/natanaelvich/app-auth-supabase-example

React Native User Management example with Expo and Supbase
https://github.com/natanaelvich/app-auth-supabase-example

authentication expo react-native supabase

Last synced: about 2 months ago
JSON representation

React Native User Management example with Expo and Supbase

Awesome Lists containing this project

README

        

# React Native User Management example with Expo

## Requirements

- Install the [Expo CLI](https://docs.expo.io/get-started/installation/)

## Setup & run locally

### 1. Create new project

Sign up to Supabase - [https://supabase.com/dashboard](https://supabase.com/dashboard) and create a new project. Wait for your database to start.

### 2. Run "User Management Starter" Quickstart

Once your database has started, run the "User Management Starter" quickstart. Inside of your project, enter the `SQL editor` tab and scroll down until you see `User Management Starter`.

### 3. Get the URL and Key

Go to the Project Settings (the cog icon), open the API tab, and find your API URL and `anon` key, you'll need these in the next step.

The `anon` key is your client-side API key. It allows "anonymous access" to your database, until the user has logged in. Once they have logged in, the keys will switch to the user's own login token. This enables row level security for your data. Read more about this [below](#postgres-row-level-security).

![image](https://user-images.githubusercontent.com/10214025/88916245-528c2680-d298-11ea-8a71-708f93e1ce4f.png)

**_NOTE_**: The `service_role` key has full access to your data, bypassing any security policies. These keys have to be kept secret and are meant to be used in server environments and never on a client or browser.

Set the details in the `/lib/supabase.js` file.

### 4. Install the dependencies & run the project:

Install the dependencies:

```bash
npm install
```

### 4a. For file picker

In order to get the file picker to work you must first prebuild the project before running it.

```bash
expo prebuild
```

### 5. Run the application

Run the application: `npm start`.

## Supabase details

### Postgres Row level security

This project uses very high-level Authorization using Postgres' Role Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.

This is a trimmed-down schema, with the policies:

```sql
-- Create a table for Public Profiles
create table
profiles (
id uuid references auth.users not null,
updated_at timestamp
with
time zone,
username text unique,
avatar_url text,
website text,
primary key (id),
unique (username),
constraint username_length check (char_length(username) >= 3)
);

alter table
profiles enable row level security;

create policy "Public profiles are viewable by everyone." on profiles for
select
using (true);

create policy "Users can insert their own profile." on profiles for insert
with
check (auth.uid () = id);

create policy "Users can update own profile." on profiles for
update
using (auth.uid () = id);

-- Set up Realtime!
begin;

drop
publication if exists supabase_realtime;

create publication supabase_realtime;

commit;

alter
publication supabase_realtime add table profiles;

-- Set up Storage!
insert into
storage.buckets (id, name)
values
('avatars', 'avatars');

create policy "Avatar images are publicly accessible." on storage.objects for
select
using (bucket_id = 'avatars');

create policy "Anyone can upload an avatar." on storage.objects for insert
with
check (bucket_id = 'avatars');
```

## License

[MIT License](./LICENSE)