Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. Tags
    3. authentication
    Log in to post

    • A

      ProGet: login not working anymore after upgrading to 22.0.2
      Support • proget authentication login • • a.diessl  

      7
      0
      Votes
      7
      Posts
      31
      Views

      A

      Thanks for your suggestion, @atripp, that's definitely something we'll look into when we find time to do so. In the meantime we have implemented the workaround described above, so thanks again for your help.
    • ?

      ProGet with Postgres database using SSL Host base authentication
      Support • proget authentication databases postgresql ssl • • Travis Illig  

      5
      0
      Votes
      5
      Posts
      69
      Views

      ?

      Thank you very much for your precision. I realy appreciate it. I personaly work with non conterize Postgres database in order to avoid data corruption issue; but I understand your make this decision. Hava a good day, Mathieu HOFERT
    • ?

      Creating Tokens for Continuous Intergration
      Support • proget npm authentication continuous-integration • • Travis Illig  

      2
      0
      Votes
      2
      Posts
      15
      Views

      ?

      You need to create an API in the ProGet UI; API Access and API keys
    • ?

      Support for Azure AD authentication
      Support • proget authentication azure cloud • • Travis Illig  

      5
      0
      Votes
      5
      Posts
      74
      Views

      ?

      I think that guide is more for when you host a domain controller in azure as IaaS. Im after connecting to Azure AD in the form of SAML, or OpenIDConnect (Federation) I'll keep an eye on release notes to see when SSO gets released. Thanks
    • ?

      Requiring authentication for Symbols/source feed without Integrated Windows Auth (IWA)?
      Support • proget npm symbols authentication • • Travis Illig  

      2
      0
      Votes
      2
      Posts
      39
      Views

      jrasch

      This will be fixed in PG-1273 for the next maintenance release.
    • ?

      Create private feeds with login option
      Support • proget nuget authentication • • Travis Illig  

      5
      0
      Votes
      5
      Posts
      51
      Views

      ?

      I can answer the first three questions pretty easily: ProGet does not support being installed as a sub-application; some users have done a reverse proxy successfully, but we really don't support that configuration The Feed url is based on the name of your feed, so it can be whatever you want. You can't do further customization. That's not a problem But I'm afraid I really don't understand the situation about 4-6. ProGet does have some extensibility hooks that you may be able to use.
    • P

      Stop auto login of "ExpressUser"
      Support • otter authentication • • pdavis_9878  

      4
      0
      Votes
      4
      Posts
      16
      Views

      atripp

      You can request it at my.inedo.com, or just ask as a note on the Otter Quote Request Form. What's nice about going through the pre-sales/quote process, is that we can work together beyond just random forum / Q&A posts, as obviously we are generally motivated to help you prove a success to enable a sale ;)
    • ?

      Using AD credentials to push nuget package not working
      Support • proget nuget authentication • • Travis Illig  

      2
      0
      Votes
      2
      Posts
      11
      Views

      atripp

      I'm afraid Linux doesn't support Windows Integrated Authentication. As a work-around, you can create a second site in IIS that points to the same path, but doesn't have Windows Integrated Authentication enabled.
    • P

      TFS extension authorization failure after upgrade to v6, and then rollback to v5.8.3
      Support • buildmaster authentication tfs • • pdickers_0718  

      6
      0
      Votes
      6
      Posts
      85
      Views

      P

      I discovered one more error detail. BuildMaster logged an error that it couldn't use the folder (for the "get latest" copy on the build server) because it belonged to a workspace for a different account. I believe this is because I changed from using a domain account to a local account on the TFS server machine for the TFS connection from the BuildMaster machine. I deleted the workspace for the previous account. I edited the TFS connection in BuildMaster, entered the account information for the local account that I am now using, and saved it without doing a "Test Connection". Now, everything seems to be working okay. This installation of BuildMaster has been through many upgrades. Maybe someday I will do a full uninstall and a clean install of the latest version, and build new applications in that version, etc. If anyone needs to know, I found (and then deleted as needed) the TFS workspaces as follows (this is using TFS 2017 and Visual Studio 2017). On my workstation with Visual Studio 2017 installed, I ran the "Visual Studio 2017"-"Developer Command Prompt". This opens a command prompt window with all the appropriate environment variables set to allow the "TF" command to be used. Then, run: tf vc workspaces /owner:* /computer:* /collection:"http://URL-for-TFS-collection/" to show all the existing workspaces (this shows username and workstation as well). To delete an existing workspace, use a command like this (note that this uses the singular form "workspace" where the previous command uses the plural "workspaces"): tf vc workspace /delete /collection:"http://URL-for-TFS-collection/" WORKSPACE-NAME;USERNAME-for-the-workspace This will let you know if there are any pending changes in the workspace, and ask if you are sure you want to delete the workspace.
    • ?

      Does ProGet support Connector to VSTS Nuget Feeds (Oauth2 Authentification)
      Support • proget feeds authentication microsoft • • Travis Illig  

      2
      0
      Votes
      2
      Posts
      21
      Views

      ?

      hi Markus, you should be able to put credentials in your Connector. Then you should be able to connect.
    • ?

      Anonymous publishing to an NPM feed
      Support • proget npm authentication publishing • • Travis Illig  

      2
      0
      Votes
      2
      Posts
      18
      Views

      ?

      I don't believe the NPM protocol allows for anonymous pushes. You could certainly have your CI put it in a drop folder however, which the ProGet would pick-up.
    • ?

      Permit AD computer accounts access via integrated auth
      Support • proget authentication integrations • • Travis Illig  

      2
      0
      Votes
      2
      Posts
      16
      Views

      ?

      If you have Windows Integrated Authentication enabled, then it will not be possible to do this. The 401 is occurring before the request even makes it to ProGet, which is how WIA is designed. You can also set up a second site in IIS without WIA enabled. That would lalow the request to get to ProGet, and if you have an "Anonymous" pseudo-user configured with permissions, then the lack of a credential will be ignored.
    • ?

      LDAP npm install fails with 401
      Support • proget npm authentication • • Travis Illig  

      3
      0
      Votes
      3
      Posts
      28
      Views

      ?

      Thanks, that fixed it.
    • ?

      Integrated Authentication Enabled but login-window still shown
      Support • proget authentication ldap • • Travis Illig  

      3
      0
      Votes
      3
      Posts
      19
      Views

      ?

      Ah, I see it. I use Caddy as my reverse proxy which doesn't support this feature.
    • ?

      How do I correctly pass username / password to a security protected Maven feed?
      Support • proget authentication java • • Travis Illig  

      3
      0
      Votes
      3
      Posts
      80
      Views

      ?

      Ok I figured out what I was doing wrong. I was setting the URL in build.gradle to: http://<user>:<password>@proget-server But it should look like this instead publishing { repositories { maven { credentials { username "$mavenUser" password "$mavenPassword" } url "http://proget-server" } } } With the mavenUser and mavenPassword being defined in ~/.gradle/gradle.properties
    • ?

      AD Schema upgrade
      Support • proget authentication • • Travis Illig  

      2
      0
      Votes
      2
      Posts
      8
      Views

      ?

      This should not impact your ProGet installation
    • ?

      Are there plans to support AuthToken authentication to the NPM feeds?
      Support • proget npm authentication • • Travis Illig  

      2
      0
      Votes
      2
      Posts
      41
      Views

      ?

      Auth tokens are now supported for npm feeds; you'll need to create the token as a ProGet API Key. Please see the API & Access Key documentation to learn more. This is an updated answer; earlier the answer mentioned the feature was not supported.
    • ?

      Feed not requiring APIKey to push package
      Support • proget api authentication permissions • • Travis Illig  

      8
      0
      Votes
      8
      Posts
      37
      Views

      ?

      The "Pull from Another Repository" actually requires the Feeds_PullPackage privilege; so make sure to grant anonymous that as well. Then it should work as expected!
    • ?

      On IIS: npm adduser fails on server with a NotSupportedException: The given path's format is not supported.
      Support • proget npm authentication • • Travis Illig  

      4
      0
      Votes
      4
      Posts
      18
      Views

      ?

      It looks like there was a regression in 4.6.0 that is causing this change in behavior. We'll have it fixed in ProGet 4.6.3, which will should be released by tomorrow at the latest.
    • ?

      SecurityException on attempting to log in with LDAP
      Support • proget authentication ldap • • Travis Illig  

      3
      0
      Votes
      3
      Posts
      8
      Views

      ?

      Verified - the problem is resolved after upgrade to 4.6.1. Thanks!
    • 1
    • 2
    • 3
    • 4
    • 1 / 4