Implements token-based authentication that grants RPC and terminal access without requiring LuCI credentials. Support technicians can connect using a short 6-character code. CLI commands: - rttyctl token generate [ttl] [permissions] - rttyctl token list - rttyctl token validate <code> - rttyctl token revoke <code> - rttyctl token-rpc <code> <object> <method> [params] RPCD methods: - token_generate: Create support token with TTL - token_list: List active tokens - token_validate: Check token validity - token_revoke: Revoke a token - token_rpc: Execute RPC with token auth (no LuCI session needed) LuCI Support Panel: - Generate code with selectable validity (30m/1h/2h/4h) - Enter code to connect to remote node - Token-authenticated RPC execution - Live token list with copy/revoke actions Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
37 lines
1000 B
JSON
37 lines
1000 B
JSON
{
|
|
"luci-app-rtty-remote": {
|
|
"description": "Grant access to RTTY Remote Control",
|
|
"read": {
|
|
"ubus": {
|
|
"luci.rtty-remote": [
|
|
"status",
|
|
"get_nodes",
|
|
"get_node",
|
|
"rpc_list",
|
|
"get_sessions",
|
|
"get_settings",
|
|
"token_list",
|
|
"token_validate"
|
|
]
|
|
},
|
|
"uci": ["rtty-remote"]
|
|
},
|
|
"write": {
|
|
"ubus": {
|
|
"luci.rtty-remote": [
|
|
"rpc_call",
|
|
"server_start",
|
|
"server_stop",
|
|
"set_settings",
|
|
"replay_session",
|
|
"connect",
|
|
"token_generate",
|
|
"token_revoke",
|
|
"token_rpc"
|
|
]
|
|
},
|
|
"uci": ["rtty-remote"]
|
|
}
|
|
}
|
|
}
|