We’ve recently updated one of our plugins on the Mozilla Marketplace as part of our ongoing enhancements. However, we’ve encountered a blocker: the account previously used to manage this plugin is no longer accessible, as the concerned individual has left the organization.
While we do have the associated key, we’re missing access to the actual account used for publishing and updates.
Would you be able to assist us in resolving this issue or guide us on the best way forward?
Before you can transfer an add-on from one account to another, the owner of each account must be able to log into their accounts and authorize or confirm the transfer. If the owner of the original account had an organization-issued email, you may be able to work with your organization’s IT department to (temporarily) access that account in order to authorize the transfer.
Hi. Thank you for your response. The add-in that we are trying to get transferred is “OpenText Functional Testing Agent.” Would it be possible for you to share the email address of the account that owns the add-in. Unfortunately, we lost the email address as well. If it is company email address, we will reach out to concerned person and have them reset it. If it is personal email, we would like to reach out to the concerned person.
If you want to check authenticity of me you can drop an email to rgullapally@opentext.com and I can respond.
We are closer to a release and this issue is escalated. Would really appreciate any help that can help resolve the issue and as soon as possible.
Sorry, but I’m not able to share private information about add-on developers or their accounts.
Normally we need the ID of an add-on in order to investigate it, but in this case I believe I was able to track down the specific add-on you mentioned. While I cannot share the developer account’s email address, I believe its safe to say that this account’s email address is not associated with your company’s domain.
Unfortunately, this also means that it may not be possible to transfer this extension to another account; if your company no longer has this account’s credentials, Mozilla won’t be able to verify the authenticity of the transfer request.
If this extension is installed via enterprise policies, you can work around this by publishing add-on and replacing the current extension’s Extensions or ExtensionSettings entry with values for the new add-on.
I should also mention that the extension doesn’t include an update_url, so to the best of my knowledge user-initiated installations will never update. The only way Firefox would update this extension is if it is installed by enterprise policies and you re-upload the latest version of the extension to the same static URL.