Navigation

    Inedo Community Forums

    Forums

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

    Posts made by kichikawa_2913

    • RE: Cannot push NuGet package to LDAP secured feed.

      I thought I did have anonymous View/Download on that feed, I did not. It's working now with the Api Key I set under administration, thank you!

      posted in Support
      K
      kichikawa_2913
    • Cannot push NuGet package to LDAP secured feed.

      Hello,

      We are running ProGet in a container using Podman instead of Docker and it looks to be operating well! We are currently running into an issue where we have LDAP enabled and are trying to have TeamCity publish built NuGet packages to a private feed.

      I created an API Key under Administration, set that API Key to impersonate an AD user that has permissions set under "Users & Tasks", and I'm getting the following:

      18:01:47 Step 11/11: Publish Packages (NuGet Publish)
      18:01:47   Attempt to publish symbol package. Symbol packages are not fully supported by TeamCity internal feed. For more details see https://confluence.jetbrains.com/display/TCDL/NuGet#NuGet-symbols
      18:01:47   push: Publish package Project\Project.2.1.0.symbols.nupkg
      18:01:47     Starting: F:\TeamCity\Agents\01\tools\NuGet.CommandLine.5.8.1\tools\NuGet.exe push F:\TeamCity\Agents\01\work\b5fafe99a9e2e5c9\Project\Project.2.1.0.symbols.nupkg -ApiKey ******* -Source https://proget.dev.private.network/nuget/internal-nuget/v3/index.json
      18:01:47     in directory: F:\TeamCity\Agents\01\work\b5fafe99a9e2e5c9\Project
      18:01:49     MSBuild auto-detection: using msbuild version '16.9.0.16703' from 'F:\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\bin'.
      18:01:50     Please provide credentials for: https://proget.dev.private.network/nuget/internal-nuget/v3/index.json
      18:01:50     Unable to load the service index for source https://proget.dev.private.network/nuget/internal-nuget/v3/index.json
      18:01:50       Response status code does not indicate success: 401 (Unauthorized).
      18:01:50     UserName:
      18:01:50     Process exited with code 1
      18:01:50     Process exited with code 1 (Step: Publish Packages (NuGet Publish))
      18:01:50   Step Publish Packages (NuGet Publish) failed
      

      I tried using username:password as the -ApiKey value as well with the same result. Only thing I notice is that there is a line that looks to be prompting for a username.

      I tried searching through older forum posts, but I'm not sure how valid they are since they are from version before v4.x for the most recent posts that I could find.....

      posted in Support
      K
      kichikawa_2913
    • RE: Run proget container as non root

      @rhessinger I was able to get the container running, validated a license, but then noticed that on the Administration page I was getting errors connecting to the messenger service:

      Messenger not connected; attempting to connect...
      Messenger connect failure: Connection refused
      Messenger not connected; attempting to connect...
      Messenger connect failure: Connection refused
      Messenger connect failure: Connection refused
      Messenger not connected; attempting to connect...
      Messenger connect failure: Connection refused
      

      I then ran the stored procedure you mentioned previously:

      EXEC [Configuration_SetValue] 'Service.MessengerEndpoint', 'tcp://127.0.0.1:6001'
      

      The messenger service is now connecting and seems to be operating as intended.

      posted in Support
      K
      kichikawa_2913
    • RE: Run proget container as non root

      @rhessinger I did not have the --expose=8080.

      I remember you adding that feature when we were working on the LDAP issues, thanks for reminding me!

      posted in Support
      K
      kichikawa_2913
    • RE: Run proget container as non root

      SIDE NOTE: The Podman run command I have in this thread mounts a root CA certificate location from the host into the container, this will not work with root-less containers. After we mount that volume we run podman exec -ti proget sh and then update-ca-certificates which won't work in root-less mode. Another method will need done to get your organization's root CA cert into the container for LDAPS.

      posted in Support
      K
      kichikawa_2913
    • RE: Run proget container as non root

      @rhessinger said in Run proget container as non root:

      echo '<?xml version="1.0" encoding="utf-8"?><InedoAppConfig><ConnectionString Type="SqlServer">'"`$SQL_CONNECTION_STRING"'</ConnectionString><WebServer Enabled="true" Urls="http://*:8080/"/></InedoAppConfig>' > SharedConfig/ProGet.config

      Creating that configuration file and mounting it worked! I did not need the environment variable ASPNETCORE_URLS anymore and just changed the port binding to -p 8080:8080. Thank you for your help!

      This worked implemented under Podman, I do not have Docker setup to test this with. I would assume it would work there as well just using Docker specific syntax with the commands.

      posted in Support
      K
      kichikawa_2913
    • RE: Run proget container as non root

      @rhessinger adding the /tcp resulted in the same error. Thank you for the information though!

      posted in Support
      K
      kichikawa_2913
    • RE: Run proget container as non root

      @rhessinger said in Run proget container as non root:

      'tcp://127.0.0.1:6001'

      I modified the database using that stored procedure you mentioned and am still getting the permissions denied.

      Is there a way to override the port the service is using? I saw in the documentation that the Windows version has a configuration file that can enable overriding the URLs, but I did not see that config in the container. Would that config file allow changing the port the service is binding to?

      posted in Support
      K
      kichikawa_2913
    • RE: Run proget container as non root

      @rhessinger I have tried to run the container by mapping internal 80 to 8080 on the host with the same permission denied result. I have checked to make sure 8080 is not being used on the host, that error is coming from inside the container, I would expect an error from Podman when calling podman run if the host port was already in use. I have gotten an error from podman when not mapping the ports because it was trying to use privileged port on the host (80).

      I'll do some testing with the Service.MessengerEndpoint port, thank you!

      posted in Support
      K
      kichikawa_2913
    • RE: Run proget container as non root

      We are actually running into this issue as well using Podman root-less containers because everything inside the container is running as the user.

      [user@serverName]$ podman run -d --userns=keep-id -v proget-packages:/var/proget/packages -v /etc/pki/ca-trust/source/anchors:/usr/local/share/ca-certificates:ro -p 8080:8080 --name=proget -e ASPNETCORE_URLS='http://+:8080' -e SQL_CONNECTION_STRING='Server=SERVERNAME;Database=ProGet;User ID=USERNAME;Password=PASSWORD' -e TZ='America/New_York' -i -t proget.inedo.com/productimages/inedo/proget:5.3.32 /bin/bash
      -- {GUID for Container} --
      [user@serverName]$ podman exec -it proget /bin/bash
      bash: /root/.bashrc: Permission denied
      [user@4c2bc39a6a24:/usr/local/proget$ id
      uid=1001(user) gid=1001(user) groups=1001(user)
      

      I think it may have to do with the Messenger Endpoint that runs on port 1000. I am able to override the front-end web app (binding to port 80) using -e ASPNETCORE_URLS='http://+:8080' but I think we are still seeing that error because of that Messenger Endpoint here:

      ProGet version is 5.3.32.11.
      Current DB schema version is 5.3.32.11.
      Starting the messenger...
      Messenger endpoint is tcp://localhost:1000
      Reading standard license list...
      Importing license list into database...
      

      Any thoughts on how to override that URL as well?

      Here are the logs:

      ProGet version is 5.3.32.11.
      Current DB schema version is 5.3.32.11.
      Starting the messenger...
      Messenger endpoint is tcp://localhost:1000
      Reading standard license list...
      Importing license list into database...
      License import complete.
      Looking for web app at: /usr/local/proget/web
      Initializing Scheduled Job Dispatcher...
      Scheduled Job Dispatcher initialized.
      Running Scheduled Job Dispatcher...
      Checking for scheduled jobs...
      Ensuring that all required scheduled jobs are configured...
      Scheduled job configuration is correct.
      Scheduled Job Dispatcher completed.
      crit: Microsoft.AspNetCore.Server.Kestrel[0]
            Unable to start Kestrel.
            System.Net.Sockets.SocketException (13): Permission denied
               at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
               at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
               at System.Net.Sockets.Socket.Bind(EndPoint localEP)
               at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.<Bind>g__BindSocket|13_0(<>c__DisplayClass13_0& )
               at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
               at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken)
               at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.TransportManager.BindAsync(EndPoint endPoint, ConnectionDelegate connectionDelegate, EndpointConfig endpointConfig)
               at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.<>c__DisplayClass29_0`1.<<StartAsync>g__OnBind|0>d.MoveNext()
            --- End of stack trace from previous location ---
               at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context)
               at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context)
               at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context)
               at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.BindAsync(AddressBindContext context)
               at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IEnumerable`1 listenOptions, AddressBindContext context)
               at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken)
               at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)
      Initializing Proxy Configuration Monitor...
      Proxy Configuration Monitor initialized.
      Running Proxy Configuration Monitor...
      Proxy Configuration Monitor completed.
      Initializing Feed Replication...
      Feed Replication initialized.
      Running Feed Replication...
      Feed Replication completed.
      Initializing Docker Upload Cleanup...
      Docker Upload Cleanup initialized.
      Running Docker Upload Cleanup...
      Docker Upload Cleanup completed.
      Initializing Connector Cache Check...
      Connector Cache Check initialized.
      Running Connector Cache Check...
      Getting list of connector responses...
      No connector responses to check.
      Connector Cache Check completed.
      
      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger we upgraded to the most recent version of ProGet using the Docker image by following these steps:

      1. Pull new image.
      2. Stop current container.
      3. Create new container using new image with a new name.
      4. Make sure CA certs are present in the container and made sure OS identifies them.
      5. Load ProGet web UI.
      6. Attempt to log in, getting incorrect credentials error.
      7. Attempt to log in with an admin user we manually created in the Built-In directory, same error.

      To resolve this; I had to bring back the old container, log in using AD, switch to Built-In directory for auth, stop old container, start new version container, log in with admin account under Built-In directory, go to Administration, update the InedoCore extension to most recent, and enable LDAP directory.

      Doesn't seem like ProGet reaches out for most recent extensions or the default installed version of the InedoCore extension should be 1.10.7. We shouldn't have this issue going forward, but I can see this being an issue later if an extension resolves issues that provide a major functionality.

      Another solution I guess that could work would be to manually download all extensions, put them in a directory on the host, and mount a volume that maps to the default extensions directory. I didn't try this out though.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger Looks like version 1.10.7 is the new version correct?

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger do you have an ETA on an actual release for the LDAP fixes?

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @atripp I'm okay with the problem shifting over to Microsoft, I was just happy to help with anything that can be resolved on your end. Ultimately, we want to use SAML, but because that's only available to use with an actual Enterprise license I needed another way to get a feel on how administering permissions felt with ProGet.

      I appreciate the time put into this and I'm glad I could help resolve some issues. @rhessinger has been super responsive and great to work with, thank you!

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger The long initial login only happened once, they have not had it since. I even had another user who never logged in attempt with LDAPS enabled again, he received the 403 message on initial attempt but was able to get in on second attempt. Neither one of his attempts were slow.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger disabled LDAPS per your instruction, all users testing were able to log in and navigate around without issues.

      Re-enabled LDAPS using the same steps, but setting them instead of removing them, users also did not see any issues.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger we currently do not have any proxy in front of the container, we will eventually have HAProxy.

      I had another user attempt to log in and it was instant. They also said that after the slow initial log in they were able to browse through the menus just fine.

      Do you want me to destroy the environment and set it up again to test without LDAPS?

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger we are at the point of having other users log in to ProGet to test, we are seeing the following messages for users who are part of an AD group that have every Task permission for any feed on their first log in attempt.

       Logged: 05/17/2021 15:13:35
       Level: Error
       Category: Web
       Message: An error occurred in the web application: Anti-CSRF validation failed because of user mismatch.
       Details: URL: http://proget.domain.network/log-in?ReturnUrl=%2F
      Referrer: http://proget.domain.network/log-in?ReturnUrl=%2F
      User: user@domain.network
      User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36
      Stack trace: at Inedo.Web.Security.AntiCsrfContext.Validate(HttpContext context)
      at Inedo.Web.PageFree.SimplePageBase.ValidatePostBackAsync()
      at Inedo.Web.PageFree.SimplePageBase.ExecutePageLifeCycleAsync()
      at Inedo.Web.PageFree.SimplePageBase.ProcessRequestAsync(HttpContext context)
      at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      

      This was using normal browser instance, not private session. After their first attempt to log in they try again and it takes about 2 or so minutes for them to finally get in authenticated as their AD user.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger I stopped/started the container again and was able to log in using an AD account from a private browser session and a normal browser session. I ran a shell in the container and ran the openssl commands again without issues.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger I updated the extension and had to stop/start the container. After those steps the test search using LDAPS worked. I did not use the bypass certificate validation option.

      I'm having issues with switching to LDAP though; I go to Administration -> under Security and Authentication -> click Change User Directory (LDAP) -> enter credentials for AD account added under Administration -> User & Tasks -> Tasks, but when I click the switch button nothing happens. I repeat the steps one or two more times and then the button switches to "Switch to Built-In". I then tried to stop/start the container and it will no longer start up, here are the logs:

      2021-05-15T12:39:28.725672513-04:00 ProGet version is 5.3.28.16.
      2021-05-15T12:39:29.217760650-04:00 Current DB schema version is 5.3.28.16.
      2021-05-15T12:39:29.226261354-04:00 Starting the messenger...
      2021-05-15T12:39:29.233061637-04:00 Messenger endpoint is tcp://localhost:1000
      2021-05-15T12:39:29.242384666-04:00 Reading standard license list...
      2021-05-15T12:39:29.244161259-04:00 Importing license list into database...
      2021-05-15T12:39:29.647671816-04:00 License import complete.
      2021-05-15T12:39:29.667862845-04:00 Looking for web app at: /usr/local/proget/web
      2021-05-15T12:39:29.681658506-04:00 Initializing Scheduled Job Dispatcher...
      2021-05-15T12:39:29.682192589-04:00 Scheduled Job Dispatcher initialized.
      2021-05-15T12:39:29.683068656-04:00 Running Scheduled Job Dispatcher...
      2021-05-15T12:39:29.695739484-04:00 Checking for scheduled jobs...
      2021-05-15T12:39:29.731570206-04:00 Ensuring that all required scheduled jobs are configured...
      2021-05-15T12:39:29.894296932-04:00 Scheduled job configuration is correct.
      2021-05-15T12:39:30.063317953-04:00 Scheduled Job Dispatcher completed.
      2021-05-15T12:39:30.070237930-04:00 info: Microsoft.Hosting.Lifetime[0]
      2021-05-15T12:39:30.070237930-04:00       Now listening on: http://[::]:80
      2021-05-15T12:39:30.070977279-04:00 info: Microsoft.Hosting.Lifetime[0]
      2021-05-15T12:39:30.070977279-04:00       Application started. Press Ctrl+C to shut down.
      2021-05-15T12:39:30.070977279-04:00 info: Microsoft.Hosting.Lifetime[0]
      2021-05-15T12:39:30.070977279-04:00       Hosting environment: Production
      2021-05-15T12:39:30.070977279-04:00 info: Microsoft.Hosting.Lifetime[0]
      2021-05-15T12:39:30.070977279-04:00       Content root path: /usr/local/proget
      2021-05-15T12:39:32.035847819-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-15T12:39:32.035847819-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/ - -
      2021-05-15T12:39:32.165785282-04:00 Initializing extensions in /var/proget/extensions...
      2021-05-15T12:39:32.210224781-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-15T12:39:32.210224781-04:00       Request starting HTTP/1.1 POST http://proget.domain.network/0x44/ProGet.WebApplication/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 0
      2021-05-15T12:39:32.308008757-04:00 Loading AWS extension from /tmp/Inedo/ExtensionCache/37543bedc11b0a94f5a597f2b9f968d2bb2cdcfe/package/net5.0/AWS.dll...
      2021-05-15T12:39:32.314608137-04:00 Loading Azure extension from /tmp/Inedo/ExtensionCache/dd663c6c8c191f7b29bfd3b150e0ae51572cc0ba/package/net5.0/Azure.dll...
      2021-05-15T12:39:32.318849973-04:00 Loading InedoCore extension from /tmp/Inedo/ExtensionCache/6499179f3ce87cb1c7d2dcadf74fcdbd2023f037/package/net5.0/InedoCore.dll...
      2021-05-15T12:39:32.334907387-04:00 Loading Clair extension from /tmp/Inedo/ExtensionCache/2aaf77763c2739acb513738b819f60b190ab5d7f/package/net5.0/Clair.dll...
      2021-05-15T12:39:32.337484374-04:00 Loading Sonatype extension from /tmp/Inedo/ExtensionCache/4bf4786f6ff2af66d3de185f9ccf150feaef6690/package/net5.0/Sonatype.dll...
      2021-05-15T12:39:32.339735147-04:00 Extensions manager initialization complete.
      2021-05-15T12:39:32.677513583-04:00 Configuring web proxy...
      2021-05-15T12:39:32.677765044-04:00 Using custom web proxy settings.
      2021-05-15T12:39:33.058825925-04:00 fail: Microsoft.AspNetCore.Server.Kestrel[13]
      2021-05-15T12:39:33.058825925-04:00       Connection id "0HM8NO02145PI", Request id "0HM8NO02145PI:00000002": An unhandled exception was thrown by the application.
      2021-05-15T12:39:33.058825925-04:00       Inedo.ProGet.Web.Security.UserNotFoundException: Exception of type 'Inedo.ProGet.Web.Security.UserNotFoundException' was thrown.
      2021-05-15T12:39:33.058825925-04:00          at Inedo.ProGet.WebApplication.ProGetHttpModule.AuthorizeRequestAsync(HttpApplication app) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E130753\Src\ProGet.WebApplication\ProGetHttpModule.cs:line 351
      2021-05-15T12:39:33.058825925-04:00          at Inedo.Web.InedoHttpModule.Inedo.Web.IAhWebModule.AuthorizeRequestAsync(HttpApplication app)
      2021-05-15T12:39:33.058825925-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:33.058825925-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:33.058825925-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:33.058825925-04:00          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
      2021-05-15T12:39:33.058825925-04:00 fail: Microsoft.AspNetCore.Server.Kestrel[13]
      2021-05-15T12:39:33.058825925-04:00       Connection id "0HM8NO02145PJ", Request id "0HM8NO02145PJ:00000002": An unhandled exception was thrown by the application.
      2021-05-15T12:39:33.058825925-04:00       Inedo.ProGet.Web.Security.UserNotFoundException: Exception of type 'Inedo.ProGet.Web.Security.UserNotFoundException' was thrown.
      2021-05-15T12:39:33.058825925-04:00          at Inedo.ProGet.WebApplication.ProGetHttpModule.AuthorizeRequestAsync(HttpApplication app) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E130753\Src\ProGet.WebApplication\ProGetHttpModule.cs:line 351
      2021-05-15T12:39:33.058825925-04:00          at Inedo.Web.InedoHttpModule.Inedo.Web.IAhWebModule.AuthorizeRequestAsync(HttpApplication app)
      2021-05-15T12:39:33.058825925-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:33.058825925-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:33.058825925-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:33.058825925-04:00          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
      2021-05-15T12:39:33.064489818-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-15T12:39:33.064489818-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/ - - - 500 0 - 1032.2865ms
      2021-05-15T12:39:33.064489818-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-15T12:39:33.064489818-04:00       Request finished HTTP/1.1 POST http://proget.domain.network/0x44/ProGet.WebApplication/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 0 - 500 0 - 853.9542ms
      2021-05-15T12:39:33.674215099-04:00 Initializing Proxy Configuration Monitor...
      2021-05-15T12:39:33.674346204-04:00 Proxy Configuration Monitor initialized.
      2021-05-15T12:39:33.674432888-04:00 Running Proxy Configuration Monitor...
      2021-05-15T12:39:33.675695760-04:00 Proxy Configuration Monitor completed.
      2021-05-15T12:39:36.494675143-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-15T12:39:36.494675143-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/ - -
      2021-05-15T12:39:36.534387936-04:00 fail: Microsoft.AspNetCore.Server.Kestrel[13]
      2021-05-15T12:39:36.534387936-04:00       Connection id "0HM8NO02145PI", Request id "0HM8NO02145PI:00000003": An unhandled exception was thrown by the application.
      2021-05-15T12:39:36.534387936-04:00       Inedo.ProGet.Web.Security.UserNotFoundException: Exception of type 'Inedo.ProGet.Web.Security.UserNotFoundException' was thrown.
      2021-05-15T12:39:36.534387936-04:00          at Inedo.ProGet.WebApplication.ProGetHttpModule.AuthorizeRequestAsync(HttpApplication app) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E130753\Src\ProGet.WebApplication\ProGetHttpModule.cs:line 351
      2021-05-15T12:39:36.534387936-04:00          at Inedo.Web.InedoHttpModule.Inedo.Web.IAhWebModule.AuthorizeRequestAsync(HttpApplication app)
      2021-05-15T12:39:36.534387936-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:36.534387936-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:36.534387936-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:36.534387936-04:00          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
      2021-05-15T12:39:36.535779899-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-15T12:39:36.535779899-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/ - - - 500 0 - 41.2354ms
      2021-05-15T12:39:37.279959202-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-15T12:39:37.279959202-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/ - -
      2021-05-15T12:39:37.317056142-04:00 fail: Microsoft.AspNetCore.Server.Kestrel[13]
      2021-05-15T12:39:37.317056142-04:00       Connection id "0HM8NO02145PI", Request id "0HM8NO02145PI:00000004": An unhandled exception was thrown by the application.
      2021-05-15T12:39:37.317056142-04:00       Inedo.ProGet.Web.Security.UserNotFoundException: Exception of type 'Inedo.ProGet.Web.Security.UserNotFoundException' was thrown.
      2021-05-15T12:39:37.317056142-04:00          at Inedo.ProGet.WebApplication.ProGetHttpModule.AuthorizeRequestAsync(HttpApplication app) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E130753\Src\ProGet.WebApplication\ProGetHttpModule.cs:line 351
      2021-05-15T12:39:37.317056142-04:00          at Inedo.Web.InedoHttpModule.Inedo.Web.IAhWebModule.AuthorizeRequestAsync(HttpApplication app)
      2021-05-15T12:39:37.317056142-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:37.317056142-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:37.317056142-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:37.317056142-04:00          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
      2021-05-15T12:39:37.317177003-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-15T12:39:37.317177003-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/ - - - 500 0 - 37.5215ms
      2021-05-15T12:39:37.674334797-04:00 Initializing Execution Dispatcher...
      2021-05-15T12:39:37.675068562-04:00 Checking for orphaned executions...
      2021-05-15T12:39:37.679198274-04:00 Execution Dispatcher initialized.
      2021-05-15T12:39:37.679268981-04:00 Running Execution Dispatcher...
      2021-05-15T12:39:37.705928199-04:00 Checking for executions to dispatch...
      2021-05-15T12:39:37.713542381-04:00 Execution Dispatcher completed.
      2021-05-15T12:39:38.190999760-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-15T12:39:38.190999760-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/ - -
      2021-05-15T12:39:38.227968562-04:00 fail: Microsoft.AspNetCore.Server.Kestrel[13]
      2021-05-15T12:39:38.227968562-04:00       Connection id "0HM8NO02145PI", Request id "0HM8NO02145PI:00000005": An unhandled exception was thrown by the application.
      2021-05-15T12:39:38.227968562-04:00       Inedo.ProGet.Web.Security.UserNotFoundException: Exception of type 'Inedo.ProGet.Web.Security.UserNotFoundException' was thrown.
      2021-05-15T12:39:38.227968562-04:00          at Inedo.ProGet.WebApplication.ProGetHttpModule.AuthorizeRequestAsync(HttpApplication app) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E130753\Src\ProGet.WebApplication\ProGetHttpModule.cs:line 351
      2021-05-15T12:39:38.227968562-04:00          at Inedo.Web.InedoHttpModule.Inedo.Web.IAhWebModule.AuthorizeRequestAsync(HttpApplication app)
      2021-05-15T12:39:38.227968562-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:38.227968562-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:38.227968562-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:38.227968562-04:00          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
      2021-05-15T12:39:38.228269535-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-15T12:39:38.228269535-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/ - - - 500 0 - 37.3348ms
      2021-05-15T12:39:38.920950517-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-15T12:39:38.920950517-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/ - -
      2021-05-15T12:39:38.957422036-04:00 fail: Microsoft.AspNetCore.Server.Kestrel[13]
      2021-05-15T12:39:38.957422036-04:00       Connection id "0HM8NO02145PI", Request id "0HM8NO02145PI:00000006": An unhandled exception was thrown by the application.
      2021-05-15T12:39:38.957422036-04:00       Inedo.ProGet.Web.Security.UserNotFoundException: Exception of type 'Inedo.ProGet.Web.Security.UserNotFoundException' was thrown.
      2021-05-15T12:39:38.957422036-04:00          at Inedo.ProGet.WebApplication.ProGetHttpModule.AuthorizeRequestAsync(HttpApplication app) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E130753\Src\ProGet.WebApplication\ProGetHttpModule.cs:line 351
      2021-05-15T12:39:38.957422036-04:00          at Inedo.Web.InedoHttpModule.Inedo.Web.IAhWebModule.AuthorizeRequestAsync(HttpApplication app)
      2021-05-15T12:39:38.957422036-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:38.957422036-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:38.957422036-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:38.957422036-04:00          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
      2021-05-15T12:39:38.957649105-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-15T12:39:38.957649105-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/ - - - 500 0 - 36.7255ms
      2021-05-15T12:39:39.678776146-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-15T12:39:39.678776146-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/ - -
      2021-05-15T12:39:39.715928593-04:00 fail: Microsoft.AspNetCore.Server.Kestrel[13]
      2021-05-15T12:39:39.715928593-04:00       Connection id "0HM8NO02145PI", Request id "0HM8NO02145PI:00000007": An unhandled exception was thrown by the application.
      2021-05-15T12:39:39.715928593-04:00       Inedo.ProGet.Web.Security.UserNotFoundException: Exception of type 'Inedo.ProGet.Web.Security.UserNotFoundException' was thrown.
      2021-05-15T12:39:39.715928593-04:00          at Inedo.ProGet.WebApplication.ProGetHttpModule.AuthorizeRequestAsync(HttpApplication app) in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp\_E130753\Src\ProGet.WebApplication\ProGetHttpModule.cs:line 351
      2021-05-15T12:39:39.715928593-04:00          at Inedo.Web.InedoHttpModule.Inedo.Web.IAhWebModule.AuthorizeRequestAsync(HttpApplication app)
      2021-05-15T12:39:39.715928593-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:39.715928593-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:39.715928593-04:00          at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
      2021-05-15T12:39:39.715928593-04:00          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
      2021-05-15T12:39:39.716044421-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-15T12:39:39.716044421-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/ - - - 500 0 - 37.4269ms
      

      Seems like there are other portions of the site that aren't using the new functionality?

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger I updated the extension and tried again; same error on the test page, nothing in the Diagnostic Center, and nothing telling in the container logs.

      Openssl commands do work over the port we use.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger That's something I forgot to double check, it does look like we use a different port. Also, sorry about the last log entries, these ones show exactly when I clicked the "Test" button on the LDAP configuration.

      2021-05-14T06:33:37.831480629-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:37.831480629-04:00       Request starting HTTP/1.1 POST http://proget.domain.network/administration/security/directories/edit?userDirectoryId=4 application/x-www-form-urlencoded 600
      2021-05-14T06:33:37.853125533-04:00 Novell
      2021-05-14T06:33:37.861160505-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:37.861160505-04:00       Request finished HTTP/1.1 POST http://proget.domain.network/administration/security/directories/edit?userDirectoryId=4 application/x-www-form-urlencoded 600 - 200 2950 text/html;+charset=UTF-8 29.6896ms
      2021-05-14T06:33:37.960908822-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:37.960908822-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/AH/AH.js?950.1.7.1 - -
      2021-05-14T06:33:37.961954750-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:37.961954750-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/AH/AH.js?950.1.7.1 - - - 200 6835 application/javascript 1.0031ms
      2021-05-14T06:33:38.008084898-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.008084898-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/icons.css?950.1.7.1 - -
      2021-05-14T06:33:38.009292550-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.009292550-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/fonts.css?950.1.7.1 - -
      2021-05-14T06:33:38.009292550-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.009292550-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/common.css?950.1.7.1 - -
      2021-05-14T06:33:38.009292550-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.009292550-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/normalize.css?950.1.7.1 - -
      2021-05-14T06:33:38.009292550-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.009292550-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/icons.css?950.1.7.1 - - - 200 530 text/css 0.7520ms
      2021-05-14T06:33:38.009292550-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.009292550-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/fonts.css?950.1.7.1 - - - 200 196 text/css 0.6669ms
      2021-05-14T06:33:38.009292550-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.009292550-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/common.css?950.1.7.1 - - - 200 859 text/css 0.6780ms
      2021-05-14T06:33:38.009292550-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.009292550-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/normalize.css?950.1.7.1 - - - 200 2608 text/css 0.6414ms
      2021-05-14T06:33:38.011058630-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.011058630-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/controls.css?950.1.7.1 - -
      2021-05-14T06:33:38.011058630-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.011058630-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/modal.css?950.1.7.1 - -
      2021-05-14T06:33:38.011058630-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.011058630-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/controls.css?950.1.7.1 - - - 200 3314 text/css 0.6005ms
      2021-05-14T06:33:38.011058630-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.011058630-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/modal.css?950.1.7.1 - - - 200 244 text/css 0.6505ms
      2021-05-14T06:33:38.052177099-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.052177099-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/styles/proget.css - -
      2021-05-14T06:33:38.052900882-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.052900882-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/styles/proget.css - - - 200 2994 text/css 0.6884ms
      2021-05-14T06:33:38.058103188-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.058103188-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.structure.min.css?950.1.7.1 - -
      2021-05-14T06:33:38.058103188-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.058103188-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.css?950.1.7.1 - -
      2021-05-14T06:33:38.058825117-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.058825117-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.structure.min.css?950.1.7.1 - - - 200 4776 text/css 0.7080ms
      2021-05-14T06:33:38.058825117-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.058825117-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.css?950.1.7.1 - - - 200 4853 text/css 0.7596ms
      2021-05-14T06:33:38.060759029-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.060759029-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.theme.min.css?950.1.7.1 - -
      2021-05-14T06:33:38.061257254-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.061257254-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.theme.min.css?950.1.7.1 - - - 200 2247 text/css 0.6159ms
      2021-05-14T06:33:38.063195885-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.063195885-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.hacks.css?950.1.7.1 - -
      2021-05-14T06:33:38.063868437-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.063868437-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.hacks.css?950.1.7.1 - - - 200 489 text/css 0.6866ms
      2021-05-14T06:33:38.068079732-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.068079732-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/styles/v5.css - -
      2021-05-14T06:33:38.068716726-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.068716726-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/styles/v5.css - - - 200 3214 text/css 0.6335ms
      2021-05-14T06:33:38.105396203-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.105396203-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/Fonts.css - -
      2021-05-14T06:33:38.106054161-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.106054161-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/Fonts.css - - - 200 196 text/css 0.6729ms
      2021-05-14T06:33:38.106865359-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.106865359-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.js?950.1.7.1 - -
      2021-05-14T06:33:38.106865359-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.106865359-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-1.11.3.min.js?950.1.7.1 - -
      2021-05-14T06:33:38.107554903-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.107554903-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-1.11.3.min.js?950.1.7.1 - - - 200 33726 application/javascript 0.6897ms
      2021-05-14T06:33:38.107728607-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.107728607-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.js?950.1.7.1 - - - 200 61388 application/javascript 0.8054ms
      2021-05-14T06:33:38.111155529-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.111155529-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_frameddialog.js?950.1.7.1 - -
      2021-05-14T06:33:38.112025380-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.112025380-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_frameddialog.js?950.1.7.1 - - - 200 1161 application/javascript 0.7622ms
      2021-05-14T06:33:38.112025380-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.112025380-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/Resources/Scripts/urls.js - -
      2021-05-14T06:33:38.113483903-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.113483903-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/Resources/Scripts/urls.js - - - 200 6294 application/javascript 0.6414ms
      2021-05-14T06:33:38.113483903-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.113483903-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_initmodal.js?950.1.7.1 - -
      2021-05-14T06:33:38.113483903-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.113483903-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_initmodal.js?950.1.7.1 - - - 200 2147 application/javascript 0.6291ms
      2021-05-14T06:33:38.175187136-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.175187136-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_formfield.js?950.1.7.1 - -
      2021-05-14T06:33:38.176021247-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.176021247-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_formfield.js?950.1.7.1 - - - 200 589 application/javascript 0.7670ms
      2021-05-14T06:33:38.367869982-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.367869982-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/icons/help.svg - -
      2021-05-14T06:33:38.368749301-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.368749301-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/icons/help.svg - - - 200 1161 image/svg+xml 0.9706ms
      2021-05-14T06:33:38.424032651-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.424032651-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/administration/security/directories/images/ui-icons_222222_256x240.png - -
      2021-05-14T06:33:38.424032651-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.424032651-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/administration/security/directories/images/ui-icons_888888_256x240.png - -
      2021-05-14T06:33:38.424453402-04:00 An "HTTP 404 Not Found" occurred in the web application
      2021-05-14T06:33:38.424563884-04:00 An "HTTP 404 Not Found" occurred in the web application
      2021-05-14T06:33:38.430435653-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.430435653-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/administration/security/directories/images/ui-icons_222222_256x240.png - - - 404 1848 text/html;+charset=UTF-8 6.2396ms
      2021-05-14T06:33:38.430435653-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.430435653-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/administration/security/directories/images/ui-icons_888888_256x240.png - - - 404 1846 text/html;+charset=UTF-8 6.5858ms
      2021-05-14T06:33:38.551773306-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      2021-05-14T06:33:38.551773306-04:00       Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/images/ui-icons_888888_256x240.png - -
      2021-05-14T06:33:38.553159723-04:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      2021-05-14T06:33:38.553159723-04:00       Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/images/ui-icons_888888_256x240.png - - - 200 6999 image/png 1.3134ms
      2021-05-14T06:33:39.882510111-04:00 Running Execution Dispatcher...
      2021-05-14T06:33:39.882510111-04:00 Checking for executions to dispatch...
      2021-05-14T06:33:39.887707048-04:00 Execution Dispatcher completed.
      

      The log entries above are from configuring for the default LDAPS port, I don't see anywhere to specifically set a port in the UI but I tried setting the "Domain controller host" field to be hostName:port and got the same results.

      EDIT: I also tested running the openssl commands to connect to our DC over the custom port and I was able to connect without issues.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @kichikawa_2913 We validated the ca certs were recognized by the container by running openssl command from within the container to an internal HTTPS URL that uses an internally signed cert and also to our domain controller over port 636 for LDAPS. Both succeeded.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger now that LDAP is working we have been testing out LDAPS. What we have done is mount a volume from the host CA cert location to the container CA cert location (/usr/local/share/ca-certificates/) and run "update-ca-certificates" in the container. Just to be safe, we then stop and start the container to ensure the application picks up the changes. We are getting the following from the container logs:

      Running Feed Replication...
      Feed Replication completed.
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 POST http://proget.domain.network/administration/security/directories/edit?userDirectoryId=4 application/x-www-form-urlencoded 599
      Novell
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 POST http://proget.domain.network/administration/security/directories/edit?userDirectoryId=4 application/x-www-form-urlencoded 599 - 200 2957 text/html;+charset=UTF-8 36.4857ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/AH/AH.js?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/AH/AH.js?950.1.7.1 - - - 200 6835 application/javascript 1.1092ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/common.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/common.css?950.1.7.1 - - - 200 859 text/css 0.9084ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/normalize.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/normalize.css?950.1.7.1 - - - 200 2608 text/css 0.8422ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/fonts.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/controls.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/icons.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/controls.css?950.1.7.1 - - - 200 3314 text/css 0.6805ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/fonts.css?950.1.7.1 - - - 200 196 text/css 0.8170ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/icons.css?950.1.7.1 - - - 200 530 text/css 0.8027ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/styles/proget.css - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/modal.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/modal.css?950.1.7.1 - - - 200 244 text/css 0.8751ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/styles/proget.css - - - 200 2994 text/css 0.9401ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.structure.min.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.css?950.1.7.1 - - - 200 4853 text/css 0.8035ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.theme.min.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.structure.min.css?950.1.7.1 - - - 200 4776 text/css 0.8797ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.theme.min.css?950.1.7.1 - - - 200 2247 text/css 0.7846ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.hacks.css?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.hacks.css?950.1.7.1 - - - 200 489 text/css 0.8334ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/styles/v5.css - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/Fonts.css - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/styles/v5.css - - - 200 3214 text/css 0.8511ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/Fonts.css - - - 200 196 text/css 0.7627ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-1.11.3.min.js?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.js?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.js?950.1.7.1 - - - 200 61388 application/javascript 0.9751ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-1.11.3.min.js?950.1.7.1 - - - 200 33726 application/javascript 1.1086ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_frameddialog.js?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/Resources/Scripts/urls.js - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_frameddialog.js?950.1.7.1 - - - 200 1161 application/javascript 0.7417ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/Resources/Scripts/urls.js - - - 200 6294 application/javascript 0.7682ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_initmodal.js?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_initmodal.js?950.1.7.1 - - - 200 2147 application/javascript 0.8164ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_formfield.js?950.1.7.1 - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/inedojq/inedojq_formfield.js?950.1.7.1 - - - 200 589 application/javascript 0.8173ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/icons/help.svg - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/styles/icons/help.svg - - - 200 1161 image/svg+xml 1.0125ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/administration/security/directories/images/ui-icons_888888_256x240.png - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/administration/security/directories/images/ui-icons_222222_256x240.png - -
      An "HTTP 404 Not Found" occurred in the web application
      An "HTTP 404 Not Found" occurred in the web application
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/administration/security/directories/images/ui-icons_888888_256x240.png - - - 404 1848 text/html;+charset=UTF-8 6.1191ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/images/ui-icons_888888_256x240.png - -
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/resources/InedoLib/jquery-ui-1.11.4/images/ui-icons_888888_256x240.png - - - 200 6999 image/png 1.2750ms
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 GET http://proget.domain.network/administration/security/directories/images/ui-icons_222222_256x240.png - - - 404 1847 text/html;+charset=UTF-8 210.0431ms
      Running Execution Dispatcher...
      Checking for executions to dispatch...
      Execution Dispatcher completed.
      info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
            Request starting HTTP/1.1 POST http://proget.domain.network/0x44/ProGet.WebApplication/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 0
      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
            Request finished HTTP/1.1 POST http://proget.domain.network/0x44/ProGet.WebApplication/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 0 - 200 30 - 1.5516ms
      

      and also the following message from the LDAP test:

      [Debug] Search term: userName
      [Debug] Filter string: (&(|(|(objectCategory=user)(objectCategory=msDS-GroupManagedServiceAccount))(objectCategory=group))(|(userPrincipalName=userName*)(sAMAccountName=userName*)(name=kichikawa*)(displayName=userName*)))
      [Debug] Building search root paths for search mode SpecificDomains...
      [Debug] Searching domain: svcbindinguser@domain.network
      
      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger looks like that fix works for LDAP! I'll have to work on testing out LDAPS, do you foresee any issues there?

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger thank you! I will work to upgrade the extension today/tomorrow and provide an update after.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger thank you for the swift response! Much appreciated.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger I also setup the AD Credentials as you said, without the "@domain.network" portion.

      posted in Support
      K
      kichikawa_2913
    • RE: Connection issues when configuring LDAP on Linux container

      @rhessinger I forgot to mention that when we get the "Invalid Credentials" error, LDAPS is off and we have a hostname set for the "Domain controller host: " setting. If I remove the domain controller setting, I get "Error: Object reference is not set to an instance of an object"

      [Debug] Search term: userName
      [Debug] Filter string: (&(|(objectCategory=user)(objectCategory=group))(|(userPrincipalName=userName*)(sAMAccountName=userName*)(name=userName*)(displayName=userName*)))
      [Debug] Building search root paths for search mode SpecificDomains...
      [Debug] Searching domain: svcbindinguser@domain.network

      posted in Support
      K
      kichikawa_2913
    • Connection issues when configuring LDAP on Linux container

      Hello,

      We are currently experiencing issues configuring LDAP on a trial license.

      ProGet: Version 5.3.28 (Build 16)
      OS: OEL 7
      Container Engine: Podman 1.4.4

      Podman v1.4.4 did not implement networks yet, we are hoping that should not cause issues.

      Steps taken to configure LDAP:

      1. Go to Administration -> Manage User Directories
      2. Click “AD Credentials”
      3. Click “Create Credential”
      4. Enter Name as “BindUser”
      5. Enter the username in format "user@domain.network"
      6. Enter the password.
      7. Save.
      8. Go back to Administration -> Manage User Directories
      9. Click to edit “Active Directory (LDAP)” Directory
      10. Set “Search mode” to “Specific list…”
      11. Set “Domains to search: (one per line)” to “domain.network,BindUser”
      12. Check “Search recursively”, “Include gMSA”, and “Use LDAPS”.
      13. Test searching for a user.
      14. Get generic connection error.
      15. Uncheck “Use LDAPS”.
      16. Test searching for a user again.
      17. Get “Invalid Credentials” error

      We have double checked the credentials are correct. There seems to be an issue with LDAPS and Linux containers, but since .NET 5 was being used we would have better integration.

      posted in Support
      K
      kichikawa_2913
    • RE: SAML and Trial License?

      @rhessinger Thank you!

      posted in Support
      K
      kichikawa_2913
    • SAML and Trial License?

      Hello!

      My organization is looking at ProGet as an internal repository for NuGet, Python, and possibly more down the road. We are currently setup and running the container on OEL 7 with Version 5.3.28 (Build 16). We want to test integrating with Okta using the SAML features, is this supported on a trial license?

      We really want to test this before purchasing because getting the LDAP integration setup is not working for us, but if SAML works with Okta we would definitely look to move towards this product.

      posted in Support
      K
      kichikawa_2913
    • 1
    • 2
    • 2 / 2