We transferred the operations map from github to gitlab. The operations map cannot access the data yet because “xxxxxxx.xxxxxxx.org” is not authorized.
We transferred the operations map from github to gitlab. The operations map cannot access the data yet because “xxxxxxx.xxxxxxx.org” is not authorized
Hi @sector, are you using one of the public KoBo servers (HHI/OCHA) or your own instance?
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
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
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.
Thank you very much for this.
If you need to fully specify, could you add https://hcr.pages.gitlab.cartong.org/ I hope this can help in moving forward.
Once again, your assistance is appreciated.
Rather odd corresponding with someone whose name is “Sector”, but I’ve replaced https://gitlab.cartong.org/ with https://hcr.pages.gitlab.cartong.org/ as requested. Please send future requests for CORS changes to email@example.com, preferably from a CartONG email address and not a Gmail address. Thanks. —John
Thank you for your response, it’s appreciated.