Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. scroak_6473
    3. Best
    S
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Best posts made by scroak_6473

    • RE: Proget Feature request - API key admin per user

      Hi @apxltd

      Your description sounds perfect. Look forward to seeing this in a future version.

      Also your software products rock! Keep up the great work!

      Thanks

      Simon

      posted in Support
      S
      scroak_6473
    • RE: BUG: ProGet Vulnerablity Listing

      Hi @atripp

      I like your "tags that use this layer" suggestion, I was also thinking you could do something like this mock-up within the repo view:

      a0a5b615-b120-408f-828d-a750d48dacfa-image.png

      In addition you could also improve the "feed view" with some more information about the number of tags/images & vulnerablities per repo like this:

      d8a7bb14-b6c6-4676-b5b6-11d25523bb2d-image.png

      Or even:

      262b93e8-7f06-4048-a50a-afe0935abadb-image.png

      posted in Support
      S
      scroak_6473
    • Proget Feature request - API key admin per user

      Hey Guys,

      Hoping to submit a feature request here.

      In Proget you should provide the ability for a user to manage their own API keys via the web interface.

      At the minute API keys need to be setup by an administrator and assigned to a user via the impersonate user field.

      It would be nice if the user was able to create their own API key via the user menu here:
      2b43f2d3-37dd-4ef0-b284-8df5dacab7ab-image.png

      Use case:

      Access to proget is setup using AD authentication and assigning an AD group (not ad user) with the correct privilege's.

      The user then needs an API key to use with CI/CD tools on the users workstation.

      Today:

      Administrator needs to login to admin portal, add the ad user with the correct "security", then generate an API key and "impersonate" the user that has just been setup.

      Required state:

      User logs into the web portal and generates their own key that inherits the users current permission set.

      Thanks

      Simon

      posted in Support
      S
      scroak_6473
    • 1 / 1