18eecaf151
## Summary cloudflared access login and cloudflared access curl fails when the Access application has warp_as_auth enabled. This bug originates from a 4 year old inconsistency where tokens signed by the nginx-fl-access module include 'aud' as a string, while tokens signed by the access authentication worker include 'aud' as an array of strings. When the new(ish) feature warp_as_auth is enabled for the app, the fl module signs the token as opposed to the worker like usually. I'm going to bring this up to the Access team, and try to figure out a way to consolidate this discrepancy without breaking behaviour. Meanwhile we have this [CUSTESC ](https://jira.cfdata.org/browse/CUSTESC-47987), so I'm making cloudflared more lenient by accepting both []string and string in the token 'aud' field. Tested this by compiling and running cloudflared access curls to my domains Closes AUTH-6633 |
||
|---|---|---|
| .. | ||
| encrypt.go | ||
| launch_browser_darwin.go | ||
| launch_browser_other.go | ||
| launch_browser_unix.go | ||
| launch_browser_windows.go | ||
| path.go | ||
| shell.go | ||
| signal_test.go | ||
| token.go | ||
| token_test.go | ||
| transfer.go | ||