You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add endpoints for register and onboard
Create a free subscription and a base tenant and attach the user to it
Sveletkit simple example
Various correction and upgrade
Naming
Other stuff
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,10 @@ SvelteKit Frontend added. (not working in Aspire with fnm), so:
14
14
15
15
`npm install, npm run dev in svelte-link-ui folder`
16
16
17
+
After all the Aspire things are mounted.
18
+
19
+
Simple onboarding endpoints + Svelle exmple. Now you can register new users and test. (Very simple and naive, but you have an example you can build on.)
20
+
17
21
## Goal
18
22
19
23
This project allows you to choose any OAuth provider and remain independent in terms of your security design. You can add any frontend (Blazor, Next.js, SvelteKit) or backend APIs in front or behind this security layer. For a full SPA, you can modify Yarp to be a full BFF (Backend for Frontend).
@@ -67,5 +71,5 @@ For your backend APIs, in the EF Core pooled DbContext factory, the user is inje
67
71
68
72
## How You Can Help
69
73
70
-
If you find this project useful, you can help by reviewing the implementation or contributing to make it more generic (user onboarding from oauth provider via webhook or other stuff). It's a side project on a boring and not "sexy" topic for me, but I hope it can be helpful to some of you. This project aims to avoid fully managed pricey solutions because, in the end, we only need simple OAuth authentication and to manage our authorization layer by ourselves. Help on that will be appreciated.
74
+
If you find this project useful, you can help by reviewing the implementation or contributing to make it more generic ~~(user onboarding from oauth provider via webhook or other stuff)~~ => simple onboarding implmented. It's a side project on a boring and not "sexy" topic for me, but I hope it can be helpful to some of you. This project aims to avoid fully managed pricey solutions because, in the end, we only need simple OAuth authentication and to manage our authorization layer by ourselves. Help on that will be appreciated.
new()//Not really used anymore because the user is not active at the top lvl (managed by you oauth provider, but inactivity is managed at subscription lvl)
0 commit comments