iam: lux-exchange was already declared; keep one entry

The exchange client existed further down the app list; the second entry would
have declared the same clientId twice. lux-vote stays.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
2026-09-04 00:07:10 -07:00
co-authored by Hanzo Dev
parent b10cc1adf6
commit e2aec201c8
-1
View File
@@ -59,7 +59,6 @@ orgs:
- { app: wallet, type: spa, hosts: [lux.network, wallet.lux.network, bridge.lux.network] } # clientId lux-wallet (was Casdoor app `app-lux`)
- { app: explore, type: spa, hosts: [explore.lux.network] } # clientId lux-explore; the live shared explorer also answers brand-themed *.lux.network and cross-brand domains — preserved via idempotent reconcile, declared per-brand when decomplected
- { app: vote, type: spa, hosts: [lux.vote] } # clientId lux-vote — luxfi/vote (vote2). spa/PKCE, never confidential (see note below)
- { app: exchange, type: spa, hosts: [lux.exchange] } # clientId lux-exchange — lux.id replaces the in-app siwx login; wallet proof happens in IAM (wallet connector), apps only consume the wallets/did claims
# lux.cloud is the LIVE console (observed: client_id=lux-cloud,
# redirect_uri=https://lux.cloud/auth/callback). cloud.lux.network is the
# older name, kept registered so it does not break if still linked.