Sree Posted May 5, 2018 Share Posted May 5, 2018 Hello Team, I have tried to integrate google sign in as adviced in the doc https://docs.whmcs.com/Configuring_Sign-In_using_Google. I added my ClientId and ClientSecret key in the WHMCS admin area sign-in-integrations page. But I'm getting the error "Invalid details not saved. Please verify your details and try again" and the following error in the browser developer console Quote {"status":"error","errorMessage":"Could not verify details for Sign In Integration \u0022Google\u0022. Connection to provider failed: Client error response https://accounts.google.com/o/oauth2/iframerpc?action=checkOrigin\u0026origin=http%3A%2F%2F<mysitename.com>\u0026client_id=<myclientid> [status code] 403 [reason phrase] Forbidden" I rechecked the API Key and Secret and also the Authorized Javascript Origins value as described in https://docs.whmcs.com/Troubleshooting_Sign-In_using_Google< But still I'm getting the same error. kindly help me to resolve this issue 0 Quote Link to comment Share on other sites More sharing options...
WHMCS ChrisD Posted May 6, 2018 Share Posted May 6, 2018 Hi @Sree This is showing a 403 Forbidden error usually permissions based, could you try creating a new set of keys, please? 0 Quote Link to comment Share on other sites More sharing options...
Sree Posted May 6, 2018 Author Share Posted May 6, 2018 8 hours ago, WHMCS ChrisD said: Hi @Sree This is showing a 403 Forbidden error usually permissions based, could you try creating a new set of keys, please? Hi @ChrisD I tried the same. But it doesn't worked as expected. 0 Quote Link to comment Share on other sites More sharing options...
inteldigital Posted May 7, 2018 Share Posted May 7, 2018 Try signing out of your Google account and back in again. Sometimes, especially if you have multiple sub accounts logged in, things can get weird. Other things to check are that you're not restricting the OAuth Client to the wrong address, you need to be restricting it from your WHMCS installation URL, which can't be a path example.com/whmcs. So it needs to be a FQDN or a subdomain of such. Bare in mind, you NEED to set the OAuth settings FIRST before trying to create credentials. Configuring Sign-In using Google 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.