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
Copy file name to clipboardExpand all lines: readme.md
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,7 @@
15
15
-[adjust local dns](#adjust-local-dns)
16
16
-[install root ca for local development](#install-root-ca-for-local-development)
17
17
-[dev notes](#dev-notes)
18
+
-[Websockets](#websockets)
18
19
-[JWT auth access and refresh token](#jwt-auth-access-and-refresh-token)
19
20
-[backend](#backend)
20
21
-[run tests](#run-tests)
@@ -405,6 +406,10 @@ Installing root-ca certificate imply that certificates generated within that wil
405
406
406
407
## dev notes
407
408
409
+
### Websockets
410
+
411
+
for websockets example [see here](https://github.com/devel0/example-webapi/blob/9f683560af83111b11fb54e1e34c071718379baa/Controllers/SampleController.cs#L35)
412
+
408
413
### JWT auth access and refresh token
409
414
410
415
- authentication and authorization are managed entirely by the backend, in fact the frontend doesn't store any access token or restore token in local storage ; from the frontend side point of view the authentication is transparently managed through the browser `X-Access-Token` and `X-Refresh-Token` that the [server][23] sets after successful login through `Set-Cookie` header ( the frontend only call the login and logout webapi without storing anything on javascript side ):
0 commit comments