We transferred the operations map from github to gitlab. The operations map cannot access the data yet because “xxxxxxx.xxxxxxx.org” is not authorized.
Is it possible you add “xxxxxxx.xxxxxxx.org” or just “xxxxxxx.org” to the list of allowed CORS origins from your end? or how should we do from our end?
Hi @Josh the account we are using is an office (Humanitarian Cluster/Sector) account that was set up by a different colleague who’s not in the unit anymore, how do I check to be sure.
Hi @sector, if your URL is kf.kobotoolbox.org then you are using HHI, if kobo.humanitarianresponse.info then OCHA. Otherwise you’ll be on a non-kobo-hosted server
Hi @sector, I have to follow the CORS specification when I configure allowed origins:
An Origin is defined by the CORS RFC Section 3.2 as a URI scheme + hostname + port, or one of the special values ‘null’ or ‘file://’. Default ports (HTTPS = 443, HTTP = 80) are optional here.
That means, unfortunately, that I can’t use trustedpartner.org as a catch all if the application that’ll contact KoBoToolbox resides at gitlab.trustedpartner.org: I have to fully specify https://gitlab.trustedpartner.org/ (replacing trustedpartner with the name of your organization).
I found previous correspondence with your organization and saw that you’re using the humanitarian server, so I added the new GitLab CORS origin for you. I’ve left the old https://trustedpartner-staff.github.io one there as well in case you’re still using it.