AnsweredAssumed Answered

Strange problem changing Oath redirect URI

Question asked by DavidMargolis_1 on Oct 24, 2017
Latest reply on Oct 24, 2017 by wimdecorte

Hi. I'm having a strange issue setting up Filemaker Server with OAuth via Google.


When I set everything up with Google I accidentally entered the wrong redirect URI. Just a stupid mistake, I used https when it should have been http.


The issue I'm having is that even though I have set up new credentials with Google and used the correct URI, Filemaker server is still using the old incorrect URI which returns a 400 error when users try to sign in by clicking on the Google button to authenticate. It's as if the URI has been cached somewhere and it can't be overwritten.


I've tried rebooting the server, stopping and starting the service, turning Google Oauth on and off and all kind of combinations of these but nothing seems to unstick the old incorrect URI.


Is this a known issue and is there a workaround?