Exposed Shared Secret — rotation requested 2 weeks ago via developer@etsy.com, no resolution #1692
Unanswered
pistilbooksonline-web
asked this question in
Q&A
Replies: 1 comment 1 reply
|
@pistilbooksonline-web did you ever get a resolution on this issue? i am running into same issue and no response from developer@etsy.com |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Confirmation
Question / discussion
Hi, I'm hoping someone from the Etsy team can help or point me in the right direction.
I'm the owner of a registered Seller App, "Pistil Books" used only to manage my own shop's (Pistilbooks) inventory. My app's Shared Secret was accidentally exposed during local development.
I reported this to developer@etsy.com on 8/2 and asked for the Shared Secret to be rotated. A support rep confirmed it was escalated to a specialized team, but that was weeks ago, and despite two follow-up emails and a message to security@etsy.com, I haven't received a resolution or new credentials.
There doesn't appear to be a self-service way to regenerate a Shared Secret from the developer dashboard — is that correct? And is there anything else I can do to help move this along?
Thanks for any help.
All reactions