Commit 3576c92
committed
Revert u2m.go client_secret handling — not needed
Earlier commits in this branch (23697e5, 0ec7e06) modified u2m.go to
avoid sending an empty client_secret on the PKCE public-app flow,
citing server rejection with "Public app should not use a client secret".
Empirical verification (2026-04-21):
- Prod Legacy (adb-6436897454825492.12.azuredatabricks.net): PASS with
unpatched u2m.go — server accepts the request.
- Stg Legacy (adb-7064161269814046.2.staging.azuredatabricks.net):
FAIL with 400 Bad Request on unpatched u2m.go.
Since the production server tolerates the current behavior, the patch
isn't strictly required for customers. Reverting to keep the PR minimal
and matching upstream main exactly for this file. If staging server
strictness later rolls out to prod, we can re-add this fix then.
Signed-off-by: Madhavendra Rathore
Signed-off-by: Madhavendra Rathore <madhavendra.rathore@databricks.com>1 parent bc4e923 commit 3576c92
1 file changed
Lines changed: 5 additions & 13 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | | - | |
32 | | - | |
33 | | - | |
34 | | - | |
35 | | - | |
36 | | - | |
37 | | - | |
38 | | - | |
39 | | - | |
40 | | - | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
41 | 33 | | |
42 | 34 | | |
43 | 35 | | |
| |||
0 commit comments