Hello Blomp team,
We're integrating Blomp as a native provider in AeroFTP (open-source desktop file manager) using the OpenStack Swift API, following your official guide.
Authentication works perfectly. We obtain a valid token from https://authenticate.blomp.com/v2.0/tokens using auth version 2 with tenantName: "storage", exactly as documented.
However, the storage endpoint returned in the service catalog (http://swiftproxy.acs.ai.net:8080/v1/AUTH_...) responds with 403 Forbidden to all subsequent requests, even with the valid token attached via X-Auth-Token.
Could you help clarify:
Is swiftproxy.acs.ai.net:8080 the correct public endpoint for external API access, or is there a different storage URL we should use?
Does the free tier require any activation step before API access is available?
Is there any additional header, token scope, or app registration process needed for third-party clients?
We already have Blomp fully wired in the app (logo, UI, translations), just waiting to flip the switch once the API access works. Happy to share request logs or do a debug session together if that helps.
Thanks!
Swift API 403 Forbidden on storage endpoint after successful authentication
Re: Swift API 403 Forbidden on storage endpoint after successful authentication
Sorry for the duplicate post, I thought the first one hadn't been sent. If you want, you can remove it and leave this one, thanks.
Status :
Who is online
Users browsing this forum: Ahrefs [Bot] and 2 guests