generated from thegrind/laravel-dockerized
50 lines
1.1 KiB
Markdown
50 lines
1.1 KiB
Markdown
# Migrating from Authentik
|
|
|
|
> [!NOTE]
|
|
> You'll need access to your Authentik postgres instance as well as a database client.
|
|
|
|
|
|
## Applications
|
|
|
|
For applications we need:
|
|
- Name
|
|
- Client ID
|
|
- Client Secret
|
|
- Redirect URI
|
|
|
|
Run the following query in your database client of choice and download it as a csv or as insert statements
|
|
if your client allows.
|
|
|
|
::: code-group
|
|
```sql [PostgreSQL]
|
|
SELECT
|
|
p.name as name,
|
|
prov.client_id,
|
|
prov.client_secret,
|
|
prov._redirect_uris->0->>'url' as redirect_uri,
|
|
now() as created_at,
|
|
now() as updated_at
|
|
FROM
|
|
authentik_providers_oauth2_oauth2provider prov
|
|
join authentik_core_provider p
|
|
on prov.provider_ptr_id = p.id
|
|
```
|
|
:::
|
|
|
|
## Users
|
|
|
|
This is a little more involved since users will need to set their password again. If you
|
|
set up email sending they'll be able to just do the "forgot password" flow. If not, you
|
|
might have to handle it a different way.
|
|
|
|
::: code-group
|
|
```sql [PostgreSQL]
|
|
select
|
|
u.name,
|
|
u.email,
|
|
'cantbenull' as password, -- This won't work as a password but password can't be null
|
|
u.uuid
|
|
from authentik_core_user u
|
|
where u.email <> ''
|
|
```
|
|
::: |