Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Permissions only work when set for specific user, not a group (LDAP)

    Scheduled Pinned Locked Moved Support
    34 Posts 5 Posters 56 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      kichikawa_2913
      last edited by

      We are now having issues just creating the container getting the following error:

      Error: error creating temporary passwd file for container 441b7e059858087ded586bf7b20a02284af788603bd6fb67e532a0021107db1c: open /home/{username}/.local/share/containers/storage/overlay/6b312eb340dc2cafa8c6aaccdec719d8c249b226b4825ada3250bafd209a607d/merged/etc/passwd: value too large for defined data type

      I don't think this is related to ProGet, so I'll report back after we get this resolved.

      1 Reply Last reply Reply Quote 0
      • Dan_WoolfD Offline
        Dan_Woolf inedo-engineer
        last edited by

        Hi @kichikawa_2913,

        I would agree that does not look like a ProGet error. Please let us know what you find.

        Thanks,
        Dan

        K 3 Replies Last reply Reply Quote 0
        • K Offline
          kichikawa_2913 @Dan_Woolf
          last edited by

          @Dan_Woolf the issues we were running into (value too large for defined data type) were related to our AV being installed and enabled on the server.

          @sebastian we updated to 6.0.10 and made sure InedoCore was up-to-date and we are still seeing issues where scoping view/download permissions to an AD group does not work but adding "Anonymous" or specific users does work.

          1 Reply Last reply Reply Quote 0
          • K Offline
            kichikawa_2913 @Dan_Woolf
            last edited by

            @Dan_Woolf working with some other team members, we found that the user we are using for the AD configuration does not have permissions to enumerate the user groups. I tried with a different user that does have permissions and view/downloading packages from the UI works fine, but from Visual Studio still does not. I tested using pre 6.0 security features and post-6.0 features with the same results.

            So part of the issue is the permissions of the user we are using in the AD configuration.

            1 Reply Last reply Reply Quote 0
            • K Offline
              kichikawa_2913 @Dan_Woolf
              last edited by

              @Dan_Woolf something else I noticed in the preview security features is that I can't find where to manage the AD credentials for the LDAP integration user. I had to revert back to pre-6.0 behavior to do it.

              1 Reply Last reply Reply Quote 0
              • Dan_WoolfD Offline
                Dan_Woolf inedo-engineer
                last edited by

                Hi @kichikawa_2913,

                For managing the AD Credentials, that will be fixed in ProGet 6.0.11. Unfortunately, that was not caught in time for the release, but it is fixed in a current development branch.

                So I just want to make sure I understand the current state.

                • You have updated the AD Credentials to use a user that can query groups.
                • When you test the permission in ProGet it shows view/download.
                • When one of those users logs into the ProGet UI, they can view and download the packages fine.
                • When they try to view and download from Visual Studio, it does not work.

                Can you confirm that is correct?

                When the user is using visual studio, are they logging in with their domain username and password? Or are they using an API key (username api the key as their password)? Can you try resetting the credentials used for visual studio? We have a walk through on how in our troubleshooting section of the how to add a repository to Visual Studio How To.

                Thanks,
                Dan

                K 1 Reply Last reply Reply Quote 0
                • K Offline
                  kichikawa_2913 @Dan_Woolf
                  last edited by

                  @Dan_Woolf All your bullets are correct and I did clear out my Visual Studio credentials; re-entering my credentials appears to have resolved the issue even with the 6.1 preview features enabled. I did not use an API key, I just entered my Windows credentials.

                  We are going to get our LDAP integration user corrected and continue to test to be sure. Thank you all for your help! It is greatly appreciated.

                  1 Reply Last reply Reply Quote 0
                  • Dan_WoolfD Offline
                    Dan_Woolf inedo-engineer
                    last edited by

                    Hi @kichikawa_2913,

                    Glad to hear it is working now. I know the NuGet client does a lot of caching on it's side, so it is very possible that resetting the credentials for Visual Studio forced a reset of that, but I'm not positive. Either way, I'm happy it is working for you now! Please let us know if you find any other issues with it.

                    Thanks,
                    Dan

                    K 1 Reply Last reply Reply Quote 0
                    • K Offline
                      kichikawa_2913 @Dan_Woolf
                      last edited by

                      @Dan_Woolf everything seems working as expected except for the following error from Visual Studio:

                      Severity Code Description Project File Line Suppression State Error Package 'Selenium.WebDriver.ChromeDriver 99.0.4844.5100' is not found in the following primary source(s): 'https://repo.dev.internal/nuget/approved-nuget/v3/index.json'. Please verify all your online package sources are available (OR) package id, version are specified correctly.

                      This error has apparently been reported since before we started working in this ticket. Should I open a new ticket to look into this one? This seems to be the only package we have this issue with, if we go directly to nuget.org we do not have this issue.

                      1 Reply Last reply Reply Quote 0
                      • K Offline
                        kichikawa_2913
                        last edited by

                        Seems to be related to versions after 95.0.4638.6900, we are able to install that version and prior without issues from ProGet.

                        1 Reply Last reply Reply Quote 0
                        • rhessingerR Offline
                          rhessinger inedo-engineer
                          last edited by

                          Hi @kichikawa_2913,

                          Could you please open another topic for the Selenium.WebDriver.ChromeDriver issue? I think that is unrelated to the authentication issue.

                          Thanks,
                          Rich

                          Products Engineer, Inedo

                          1 Reply Last reply Reply Quote 1

                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                          With your input, this post could be even better 💗

                          Register Login
                          • 1
                          • 2
                          • 2 / 2
                          • First post
                            Last post
                          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation