Following on my last comment, I agree with what Brightsilence said. You probably dont want to be creating projects on a per-customer basis because you can handle the need for clean managemnt in other ways. I think I remember another thread about this. If I can find it will edit this post and drop it below for reference
ETA: I think this may be relevant, let us know however:
Hi,
I’ve been playing around with uplink/tardigrade and have started using the access.Share functionality in the uplink go library. What I’ve read and noticed is that for any combination of Bucket/Prefix/Permissions the serialized access token is always the same. I was wondering if there was any way to create multiple serialized access tokens for the same combination of Bucket/Prefix/Permissions.
The application is for a medical data project. Where the buckets would be patients and the access …
I’m having a minor panic attack looking at a new change in Tardigrade. The API keys are no longer what is granted and only access grants.
Which now for one need passphrases, and two, are no longer stand alone API keys.
These are granted from what? An API key linked to my account? Our users should have stand-alone top level access that is irrevocable by no one other than themselves. We don’t want to be the master control for our user’s data.
My biggest question here is: Is the access grant a …
Hi all,
I’m trying to create a shared access with a bucket/prefix. I’m able to create a shared serialized access. I try to then use that serialized access to call to upload and I get “Unauthorized API credentials”. It’s worth mentioning that the upload works fine with a bucket/prefix when I use the serialized access created from the tardigrade api token. It’s also worth mentioning that when I don’t send in a prefix to the share, with only a bucket, I’m also able to upload.
Here’s my code for t…
4 Likes