I’m seeing same issue. I believe it is with Netlify CMS, because the question is how does the CMS (running in client code) know which Auth provider to use? It defaults to
https://api.netlify.com according to backend docs.
So that gets my client code calling netlify APIs, but how does netlify know where that request is coming from? I was hoping it would be based on the
repo field added to backend, but it doesn’t seem to work,.
What is very strange to me is that I can run this locally, but publishing to a real domain fails. I am including a brief screencast of this issue and live site. ( I did notice the
site_domain field that may explain why it works locally, but setting it explicitly to
cms.netlify.com doesn’t work in prod either, the auth succeeds but never sends back to client.)
Video -> https://edwardawebb.com/netlify-issues.mov