The issue involves fixing OAuth redirect URL generation in a self-hosted environment.
The issue reports that the OAuth redirect URL defaults to HTTP in a self-hosted setup, which Microsoft rejects as insecure. The fix likely involves modifying URL generation to respect HTTPS when behind a reverse proxy. The main blocker is understanding how the current URL generation interacts with reverse proxy setups.
Title says it all: the generated redirect URL is defaulted to HTTP on my self hosted setup, and Microsoft won't accept this as secure. I use reverse-proxy setup and am thus able to reach the frontend through https://my-domain.com, but then, probably the stack communicates internally through http endpoints and thus generates http://..... redirect URL.
What can I do to solve this?
Output of bench version
(paste here)
(paste here)
OS version / distribution, Frappe install method, etc.
Claim this issue to let others know you're working on it. You'll earn 20 points when you complete it!