@powerhousedao/academy 4.0.0 → 4.0.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/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,13 @@
|
|
|
1
|
+
## 4.0.1 (2025-07-25)
|
|
2
|
+
|
|
3
|
+
### 🚀 Features
|
|
4
|
+
|
|
5
|
+
- **switchboard,config,reactor-api:** handle auth in reactor-api ([f33c921ee](https://github.com/powerhouse-inc/powerhouse/commit/f33c921ee))
|
|
6
|
+
|
|
7
|
+
### ❤️ Thank You
|
|
8
|
+
|
|
9
|
+
- acaldas @acaldas
|
|
10
|
+
|
|
1
11
|
# 4.0.0 (2025-07-24)
|
|
2
12
|
|
|
3
13
|
This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
|
package/docs/academy/02-MasteryTrack/03-BuildingUserExperiences/07-Authorization/02-Authorization.md
CHANGED
|
@@ -1,10 +1,10 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Reactor API Authorization
|
|
2
2
|
|
|
3
|
-
This tutorial explains how to configure authorization for the Powerhouse
|
|
3
|
+
This tutorial explains how to configure authorization for the Powerhouse Reactor API using the new role-based authentication system.
|
|
4
4
|
|
|
5
5
|
## Basic configuration
|
|
6
6
|
|
|
7
|
-
The
|
|
7
|
+
The Reactor API supports two main ways to configure authorization:
|
|
8
8
|
|
|
9
9
|
1. Using environment variables
|
|
10
10
|
2. Using the powerhouse configuration file
|
|
@@ -33,13 +33,11 @@ Alternatively, you can configure authorization in your `powerhouse.config.json`:
|
|
|
33
33
|
|
|
34
34
|
```json
|
|
35
35
|
{
|
|
36
|
-
"
|
|
37
|
-
"
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
"admins": ["0x123", "0x456"]
|
|
42
|
-
}
|
|
36
|
+
"auth": {
|
|
37
|
+
"enabled": true,
|
|
38
|
+
"guests": ["0x789", "0xabc"],
|
|
39
|
+
"users": ["0xdef", "0xghi"],
|
|
40
|
+
"admins": ["0x123", "0x456"]
|
|
43
41
|
}
|
|
44
42
|
}
|
|
45
43
|
```
|
|
@@ -65,14 +63,14 @@ The new authorization system implements role-based access control with three dis
|
|
|
65
63
|
|
|
66
64
|
## Docker configuration
|
|
67
65
|
|
|
68
|
-
When running the
|
|
66
|
+
When running the Reactor API in Docker, you can pass these configurations as environment variables:
|
|
69
67
|
|
|
70
68
|
```bash
|
|
71
69
|
docker run -e AUTH_ENABLED=true \
|
|
72
70
|
-e GUESTS="0x789,0xabc" \
|
|
73
71
|
-e USERS="0xdef,0xghi" \
|
|
74
72
|
-e ADMINS="0x123,0x456" \
|
|
75
|
-
your-
|
|
73
|
+
your-Reactor API-image
|
|
76
74
|
```
|
|
77
75
|
|
|
78
76
|
## Authorization flow
|
|
@@ -95,6 +93,6 @@ If you encounter authorization issues:
|
|
|
95
93
|
|
|
96
94
|
1. Check that AUTH_ENABLED is set appropriately
|
|
97
95
|
2. Verify wallet addresses are correctly formatted in their respective roles
|
|
98
|
-
3. Check the
|
|
96
|
+
3. Check the Reactor API logs for detailed error messages
|
|
99
97
|
4. Verify that your database and Redis connections are working
|
|
100
98
|
5. Confirm that users are assigned to the correct roles
|