feat: Support direct access token auth, auto device discovery, and du…#6
feat: Support direct access token auth, auto device discovery, and du…#6veerkak wants to merge 1 commit into
Conversation
|
|
||
| The app supports two authentication modes. Choose one — do not set both. | ||
|
|
||
| ### Option 1: If you have an Access Token |
There was a problem hiding this comment.
Lets include the docs link to show where to get these tokens & why you would use one or the other?
|
|
||
| Open [http://localhost:3000](http://localhost:3000) in your browser. | ||
|
|
||
| ## Authentication |
There was a problem hiding this comment.
Devs would still need all the back end urls right to get the token right?
Can we make this clearer / provide an easy way for them to simulate this?
There was a problem hiding this comment.
No need of this set-up with Playground feature READ.ME latest should cover this.
| RING_CLIENT_SECRET=your_client_secret_here | ||
|
|
||
| # Ring Device | ||
| NEXT_PUBLIC_RING_DEVICE_ID=your_device_id_here |
There was a problem hiding this comment.
Can we include doc links on where these would be received from?
There was a problem hiding this comment.
Done included Playground Link for clarity.
veerkak
force-pushed
the
feat/access-token-auth-and-auto-discovery
branch
from
aa70193 to
d0c20a9
Compare
… API scripts, and dual UI modes - Add RING_ACCESS_TOKEN support (direct token, no client credentials needed) - Preserve existing RING_REFRESH_TOKEN flow (requires client_id + client_secret) - Error if both are set simultaneously - Auto-discover devices via GET /v1/devices when NEXT_PUBLIC_RING_DEVICE_ID not set - Access token mode ignores NEXT_PUBLIC_RING_DEVICE_ID (always auto-discovers) - Stream route accepts deviceId from frontend (after discovery) - Simplified live-view-only UI in access token mode - Full dashboard (events, processors, webhooks) in refresh token mode - Add /api/ring/config endpoint for frontend auth mode detection - Add scripts/ folder with 8 Python scripts for calling Ring APIs - Each script is standalone, prints curl equivalent, auto-discovers device - Interactive explore_apis.py menu for trying all APIs - Comprehensive README restructured for first-time users (Step 1/2/3) - Doc links for tokens, credentials, and device IDs throughout - .env.example updated with doc links for all values
veerkak
force-pushed
the
feat/access-token-auth-and-auto-discovery
branch
from
d0c20a9 to
3aa4b70
Compare
giolaq
left a comment
giolaq
left a comment
There was a problem hiding this comment.
In the PR description is written that RING_API_BASE_URL is configurable but here we are using a default one, can we add the RING_API_BASE_URL to the .env.example and use the variable ?
I found this multiple times where API_BASE is used
|
LGTM |
3 participants
Uh oh!
There was an error while loading. Please reload this page.