Fix socks5 proxy auth code handling and device auth UI#2115
Fix socks5 proxy auth code handling and device auth UI#2115
Conversation
- Cache remote device auth credentials in .tavern-auth file - Update RDA HTTP endpoint to return generated verification URIs - Print scannable QR code during CLI remote device authentication - Update DeviceAuth React component to prepopulate URL device-code - Fix DeviceAuth Revoke handler to send userCode instead of node.id Co-authored-by: KCarretto <16250309+KCarretto@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Summary
Previous Results
Insights
Slowest Tests
🎉 No failed tests in this run. | 🍂 No flaky tests in this run. Github Test Reporter by CTRF 💚 |
Fixes the remote device authentication flow for
./bin/socks5and CLI tools..tavern-authlocally upon successful authentication./auth/rda/codeAPI to return a populatedverification_uriandverification_uri_completedepending on the request host.github.com/skip2/go-qrcodeas a dependency and utilized it to print a scannable ASCII QR code to the CLI for easy device authentication./profilepage with thedevice-codequery parameter using react router hooks.DeviceAuth.tsxwherenode.idwas passed instead ofnode.userCode.PR created automatically by Jules for task 8863455242053099640 started by @KCarretto