fix: use backend identity for remote OpenClaw gateway fallback#12
Closed
moltar-bot wants to merge 2 commits into
Closed
fix: use backend identity for remote OpenClaw gateway fallback#12moltar-bot wants to merge 2 commits into
moltar-bot wants to merge 2 commits into
Conversation
Contributor
|
Superseded by # (), which rolls up all commits currently on moltar-forge:main relative to bymosbot:main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
openclawGatewayClientto identify asgateway-client(mode: backend) when device auth env vars are missingopenclaw-control-uiidentity for that fallback pathWhy
For remote HTTPS/WSS OpenClaw deployments, using a Control UI client identity without device credentials can trigger:
control ui requires device identity (use HTTPS or localhost secure context)This change keeps device-auth flow intact when configured, but makes the non-device fallback use a backend identity that works with shared gateway auth tokens in server-to-server scenarios.
Validation
npm test -- src/services/openclawGatewayClient.test.jsFixes #1
Migrated PR source from
moltar-bot:fix/openclaw-remote-gateway-authtomoltar-forge:fix/openclaw-remote-gateway-auth.Supersedes #4.