General

Welcome to MyGet’s UserVoice forum! We encourage you to leave some feedback about missing features, stuff you wish for us to include in MyGet, …

  1. API access to functionality

    It would be great to have an API to automate certain tasks on MyGet!

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. ADFS / token restriction / Credential Provider workflow support

    I'm hoping that a more secure ADFS experience/workflow can be created. I would like to see a situation where an administrator can restrict token-based authentication for feed consumers and the consumers can use some sort of Nuget ADFS CredentialProvider to authenticate against the feed. (Perhaps with single-use, short-lived tokens generated by the provider?) That way when an AD account is disabled there is no need to secondarily disable a myget account.

    https://www.visualstudio.com/en-us/docs/package/nuget/auth

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support for WAAD authentication

    Please support Windows Azure Active Directory for private feeds.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Make feed names in URLs case-insensitive.

    Situation: TeamCity build definitions with project names that contain capital letters. There are build templates that use the project name variable to do all sorts of things, from pulling from GitHub through to publishing packages.

    MyGet forces all feed names to be lower-case, which means that we can't use project name variables to push to a MyGet feed.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Ability to create "Service" users who don't have an email address and aren't linked tro an identity provider

    I would like to set up user accounts for our Build Servers that publish packages and our Octopus Deploy server that needs read only access to our Package Feeds.

    Currently I can't set this up as the users in question are obviously not people and don't have email addresses for them.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base