Appendix A: Troubleshooting Google CSE

in the early stages of the google cse beta, you might encounter errors with no clear resolution guidance, such as the ones described in the following sections error 404/not found on callback url you might get a 404 during testing when your idp redirects to this url after login (for example, when you’re uploading a new file) for one of the following causes (during google cse beta) google needs to whitelist your user or issuer (during google cse beta) you signed into several google accounts, and the test user is not the default user on your browser try to log out of all accounts and only sign into the target test account alternatively, use incognito mode in chrome with only the target test account an error occurred with the identity provider service this can manifest as an error saying one of the following messages an error occurred with the identity provider service can’t decrypt file (something went wrong and your file wasn’t downloaded) an error occurred with identity provider service the following options are possible causes (during google cse beta) your browser did not yet authenticate with your idp within drive google com to authenticate during beta, upload a drive file first, go through an upload failure , and force reauthentication as described in the next section then you can go back to your original task (opening file, updating doc, and so on) your idp is misconfigured, such as the user you are logged in with was not assigned to the idp app, the wrong client id in the cse configuration, and so on to debug, you can observe the browser network tab or ask google upload failure you can see an upload failure on drive google com when you are uploading an encrypted file and have not yet been authenticated on this browser to resolve, select the exclamation mark in a red circle (!) shown with this error this forces re authentication re authenticating through the encrypted file upload workflow fixes other authentication issues around the drive/docs apps that don’t yet have their own robust auth error handling mechanism