sonatype / nexus-public

Sonatype Nexus Repository Open-source codebase mirror
https://www.sonatype.com/products/repository-oss-download
Eclipse Public License 1.0
1.91k stars 565 forks source link

Lost access to our published artifacts #244

Closed ivanqenta closed 1 year ago

ivanqenta commented 1 year ago

Hello,

my company (Apto Payments) has been acquired by another company (Qenta Payments). At Apto Payments we maintained a series of artifacts in sonatype nexus (Developer Id = AptoPayments). The previous mobile developers are not longer with our company, and additionally, our email addresses have changed (mine, for example, was ivan@aptopayment.com, not it is ivan.oliver@qenta.com).

We need to publish new versions of our artifacts, and we don’t know how to regain access to do that. Is there a mechanism to demonstrate that we are the maintainers of these artifacts and get access to them again?

All the best,

Ivan Oliver

IdanAdar commented 1 year ago

We too are unable to reset our password - no email.

ivanqenta commented 1 year ago

Hello @nblair can I ask you if there are any updates here?

nblair commented 1 year ago

There are instructions here to reset the built in administrator password: https://support.sonatype.com/hc/en-us/articles/213467158-How-to-reset-a-forgotten-admin-password-in-Sonatype-Nexus-Repository-3

Let me know if that covers what you need.

ivanqenta commented 1 year ago

Hello @nblair thanks for your response! The problem is that we don't have access anymore to the aptopayments email address, what we need is to update the email address too, not just the password. What would we need to provide you to demonstrate that we are the same company but with a different email ldomain?

Thanks,

Ivan

nblair commented 1 year ago

@ivanqenta are you talking about your own deployment of Nexus Repository (which is what this issue tracker is for), or are you talking about artifacts published to Maven Central? In the case of the latter, you will need to create an account at https://issues.sonatype.org/browse/OSSRH and file an issue there.

ivanqenta commented 1 year ago

Thank you @nblair ! I created a ticket in maven central, I'm closing this ticket. Thanks again!