Authentication against private gitlab instance

[dosper7]

Hello, I've seen you comment in here but reading your github readme.md file you mentioned this:

Authentication is outside the scope of this project. However, I've tested both Personal Access Tokens and OAuth. They work just fine.

However, I'm not understanding how are you doing the authentication. If I understood correctly, this library generates the nuget package with the correct gitlab links, so source link works well. I've used and tested this library, I have a CICD pipeline that packs and pushes the nuget to our private nuget registry (in gitlab).

When I consume the nuget in a consumer project in my local machine, the nuget comes without that info. I use the same command locally as in the pipeline.

can you help clarify?

[Genbox]

It depends on the IDE used (and the underlying tooling). Ideally, your IDE should connect to the authenticated endpoint and get a 401 (Unauthorized) response. In that case, the IDE should redo the request but use credentials from a credential manager.

I use Jetbrains Rider, and the way it works, is to send a HTTP HEAD request to the server, it gets a 404 response back from GitLab (self managed), then it asks the user for credentials.

I enter the credentials (username + personal access token) and GitLab now authorizes the request.

The credentials are then saved to Windows Credential Manager and automatically used on the next requests.

I haven't tried it with any other IDE, but they should support authenticated requests to GitLab, GitHub, etc. already. The source link provider I've made, simply creates the correct links to the source files, everything else should be handled as with any other provider.