Globus app invalid_client, Bad signed URL; error in transfer

[William Hahn]

Any globus experts? I've been having issues setting up globus with the globus-dataverse external tool.
I'm testing with a POSIX gateway / collection. I have tested globus as a native app / non-native app, as enabling native app prevented me from referencing an identity for the registered app to give admin privs, and from generating a client secret. (Should it be registered as a native app to work with dataverse?)
When testing with a non-native app, my GCP endpoint isn't loaded in the UI and I get two 401 responses when attempting to upload with globus – 'invalid_client' and 'Bad signed URL'. I tried connecting after disabling Anubis, and still got the same responses.

When testing it registered as a native app, my local filesystem via GCP is loaded, but I get the message 'There was an error in transfer submission. BIIG' when attempting to transfer a file. Any pointers here? And should it be registered as a native app? I do notice the redirect to https://auth.globus.org/v2/web/auth-code when native app is enabled, which seems to be needed here.

As a native app, the error in transfer submission throws a 401 for a requestGlobusUploadPaths api call. I suspect this issue would be solved if there were an identity provided for registered native apps (so that I could assign it admin privs).

[Kirill Batyuk]

Hi William,

The app should be registered as a portal and as a native application (thick client).

Did you add the redirects in the configs?

The Client ID in config.json is the client ID of the native app.

 

How is your application set up? Are you running it on a dedicated server or on the same server? Do you have an SSL certificate installed? Globus does not work well without a certificate.

 

-Kirill

 

 

From: dataverse...@googlegroups.com <dataverse...@googlegroups.com> On Behalf Of William Hahn
Sent: Tuesday, November 25, 2025 10:40 AM
To: Dataverse Users Community <dataverse...@googlegroups.com>
Subject: [EXTERNAL] [Dataverse-Users] Globus app invalid_client, Bad signed URL; error in transfer

 

You don't often get email from wsh...@gmail.com. Learn why this is important

This email originated outside of WHOI. Please use caution if clicking on links or opening attachments.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/613fdb21-c726-490d-8bf1-cefadf994a2cn%40googlegroups.com.

[William Hahn]

Hi Kirill,

The main thing I was missing actually was the portal! Thanks a bunch for your suggestion; I was able to upload with the portal's clientId:clientSecret as the basic token, in conjunction with a thick client.

In case anyone else has similar problems: the application is set up on the same server as my test dataverse installation. I have SSL set up. For the portal, I added redirects for the upload, download, download-file, and base paths. I included the same redirects, as well as the same paths for localhost per Deirdre's suggestions on Zulip. Feel free to note any other important considerations if you have any.

Thanks,

William

[Kirill Batyuk]

Great! I’m glad you were able to figure it out!

-Kirill.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/a05b9424-1334-4fd4-95b5-1ef5fb7d9865n%40googlegroups.com.