gearnode
1a6e68f13c
Add email confirmation
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-12 12:17:21 +01:00
gearnode
01af3812c4
Enforce allowed tenant in each request
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-12 10:14:49 +01:00
gearnode
9688f51bc5
Style
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-11 17:37:45 +01:00
gearnode
df2795069b
Fix signup session already expired
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-11 17:37:28 +01:00
gearnode
019f76ecfd
Refactor authentication handler
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-11 12:28:51 +01:00
gearnode
5bdc474aef
Move coredata outside probo service
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-11 09:38:36 +01:00
gearnode
3c1a0c9d6d
Fix broken user manager migration
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-11 09:14:08 +01:00
gearnode
58eda95d93
Rewrite the global id system to include tenant id
...
The API should be aware of the tenant they are working on. Many solution
is possible like passing a header, adding the tenant id in each function
call, encode the tenant id in the GID.
I consider the header as a hack it force the client to keep in mind to
pass this header, having to returns an error in case of not defined
header and add a non standard header make the API more harder to use.
Passing the tenant id everywhere will be a good option but since Relay
impose to have node(id: ID!) Node interface it is not possible or by
hacking by wrapping node(id: ID!) Node in top query who getting the
tenant_id.
I finish by simpliy encode the tenant id directly in the object id, it
what AWS do too, it allow to always have the information, and it ensure
a right data isolation.
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-10 13:54:55 +01:00
gearnode
65f2245167
Fix migration organization ref
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-06 10:21:33 +01:00
gearnode
b539abf5f0
Fix migration error
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-06 10:20:13 +01:00
gearnode
9526061861
Add data to session and floating duration
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-05 17:26:07 +01:00
gearnode
cf12d3966e
Replace pgx.NamedArgs to pgx.StrictNamedArgs
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-02 08:48:52 +01:00
gearnode
bb463be895
Refactor sql row can using collectable rows
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-03-01 23:09:15 +01:00
gearnode
3ee3b37dac
Add missing fullname for signup
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-02-25 23:24:52 +01:00
gearnode
0c176674a0
Add multi-tenant system
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-02-25 22:52:06 +01:00
gearnode
e9ae77a4a0
Add login/register logic
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-02-25 17:32:26 +01:00
gearnode
743ec49972
Fix pagination
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-02-12 14:18:50 -08:00
gearnode
89fce182d2
Add login logic
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-02-04 16:22:48 -08:00
gearnode
eafc4c99c5
Update coredata user
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-02-04 15:48:16 -08:00
gearnode
4614c31ef6
Add way to hash password
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-02-04 15:48:06 -08:00
gearnode
41b957f21b
Update usrmgr schema
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-02-04 15:47:57 -08:00
gearnode
0e9746bbee
Bootstrap user manager
...
Signed-off-by: gearnode <bryan@frimin.fr >
2025-02-02 11:37:35 -08:00