bezzie 0.1.7 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -0
- package/package.json +12 -2
package/README.md
CHANGED
|
@@ -56,6 +56,14 @@ Done. Your app now has BCP212-compliant BFF auth.
|
|
|
56
56
|
|
|
57
57
|
---
|
|
58
58
|
|
|
59
|
+
## Demo
|
|
60
|
+
|
|
61
|
+
See the full BFF flow in action: [bezzie-demo.neilmason.dev](https://bezzie-demo.neilmason.dev)
|
|
62
|
+
|
|
63
|
+
Source: [github.com/neilpmas/bezzie-demo](https://github.com/neilpmas/bezzie-demo)
|
|
64
|
+
|
|
65
|
+
---
|
|
66
|
+
|
|
59
67
|
## Why
|
|
60
68
|
|
|
61
69
|
Most OAuth libraries hand tokens directly to the browser. BCP212 says you shouldn't — it's a significant attack surface. Bezzie keeps tokens server-side in Cloudflare KV and gives the browser a session cookie instead.
|
package/package.json
CHANGED
|
@@ -1,13 +1,23 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "bezzie",
|
|
3
|
-
"version": "0.1
|
|
3
|
+
"version": "0.2.1",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"sideEffects": false,
|
|
6
6
|
"engines": {
|
|
7
7
|
"node": ">=18"
|
|
8
8
|
},
|
|
9
9
|
"description": "BFF OAuth 2.0 auth library for Cloudflare Workers",
|
|
10
|
-
"keywords": [
|
|
10
|
+
"keywords": [
|
|
11
|
+
"hono",
|
|
12
|
+
"cloudflare-workers",
|
|
13
|
+
"oauth",
|
|
14
|
+
"oidc",
|
|
15
|
+
"auth",
|
|
16
|
+
"bff",
|
|
17
|
+
"session",
|
|
18
|
+
"jwt",
|
|
19
|
+
"pkce"
|
|
20
|
+
],
|
|
11
21
|
"main": "dist/index.js",
|
|
12
22
|
"types": "dist/index.d.ts",
|
|
13
23
|
"exports": {
|