# Anonymous Access, nuget push and api keys

**URL:** <https://community.sonatype.com/t/anonymous-access-nuget-push-and-api-keys/10322>\
**Category:** Sonatype Nexus Repository\
**Tags:** nexus-repository\
**Created:** [March 17, 2023, 10:57am UTC](https://community.sonatype.com/t/anonymous-access-nuget-push-and-api-keys/10322 "2023-03-17T10:57:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![emiliogonzalez](https://avatars.discourse-cdn.com/v4/letter/e/9fc29f/32.png) [@emiliogonzalez](https://community.sonatype.com/u/emiliogonzalez)\
**Post date:** [March 17, 2023, 10:57am UTC](https://community.sonatype.com/t/anonymous-access-nuget-push-and-api-keys/10322/1 "2023-03-17T10:57:05Z")

</div>

Hi everyone.

I’m right in the middle of a POC to evaluate which changes need to be made if “Anonymous Access” is disabled in Nexus… and here’s my first problem. Some CI/CD processes rely on a “nuget push” when artifacts need to be uploaded to Nexus and, as of now, with “Anonymous Access” still enabled, they work like a charm. However, yesterday I bumped into [this post](https://support.sonatype.com/hc/en-us/articles/360051896134-nuget-push-Prompts-for-Credentials-when-Anonymous-Access-is-not-Enabled) and after a quick reading I understand that, in this nuget case, “Anonymous Access” can’t be disabled as such but rather it has to be reconfigured to a different user for which a certain role with limited access has been created.

Am I right in thinking that?

Thanks for your help