Is there a possibility to authenticate to GitHub as an GitHub App and publish packages as the GitHub App identity from Jenkins? Personal access tokens can be used but they use an identity of a separate user.
Related
I am working on adding a proxy for Github Hosted maven repo. I have created the proxy and gave the remote storage url value as github url.
Anyone aware of how we can set up credentials for Nexus repo manager to talk to Github Repo. I am new to this stuff, so any help would be highly appreciated. I am guessing we might need to setup some generic user in github and created authentication token and use those for nexus to talk to Github?
Thanks in advance.
I setup a CodeArtifact maven repository and I'm able to manage artifacts dependencies during CI. I'm aslo able to retrieve an authorization token from CodeArtifact in order to fetch dependencies on local machine during development.
The problem is that the AUTH token expires after 12 hours and I'm forced to renew it.
Is there a way to setup a settings.xml file in .m2 folder in order to manage CodeArtifacts maven repositories avoiding the token refresh?
We're working in a shared repository where we're not the owner. Our AAD accounts have been invited - username#domain.com. We have no issues accessing the Git repo.
THE ISSUE: We can't access the NuGet repo. We can access it in ADO and see all the artifacts. However, when we try to pull the repo in VS, we get a 401 Unauthorized.
The workaround is to use a personal Microsoft Account (MSA). That's understandably not a good idea - it's customer work.
THE QUESTION: Is ADO's NuGet feature only supported by MSA and not AAD accounts when the invited AAD account isn't part of the owner organization? Is this a hard limit?
Thanks!
Authentication with Azure Artifacts can be a bit of a pain... but it works (even with guest AAD accounts). I am using it like this every day. If you can download the file from the feed via the UI, you will also be able to download it via VisualStudio or other tools.
VisualStudio should have no issue at all when talking to the feed, at least if it is a somewhat current version. For VSCode and others you should try the Azure Artifacts Credential Provider and run something along these lines: dotnet restore --interactive
I've seen that Octopus Supports LDAP integration.
But does it support SAML 2.0 or ADFS integration?
No. Your stuck with windows or forms based authentication.
If you are using Active Directory Authentication with Octopus, there
are two ways to sign in.
Integrated authentication Forms-based
http://docs.octopusdeploy.com/plugins/servlet/mobile#content/view/3048127
ADFS would require changes to server side code which isn't open source.
The Octopus Server -> Tentacle communication uses Public-key cryptography. Perhaps you can alter your design to keep the Octopus Server somewhere accessible and an Octopus Tentacle in the ADFS environment.
http://docs.octopusdeploy.com/display/OD/Octopus+-+Tentacle+communication
I have an organization's private GitHub repository that I am trying to connect a Heroku app to, using the Heroku Dashboard from a browser. In the settings of my GitHub account (that is linked to Heroku), under OAuth Applications, I can see Heroku Dashboard, and under Permissions, it says Full control of private repositories.
However, when I navigate to the Heroku app page and select this GitHub repo from the select-list and click Connect, I get the message:
Item could not be modified:
Admin access to repository required
On GitHub, my account has Write access for the repo. Moreover, as mentioned above, Heroku Dashboard has Full control of private repositories. Can anybody help me figure out what access needs to be granted where? I would really appreciate that.
Never mind. That private GitHub repo had been created by someone else who had since left the company. I had Write access but that is not enough. When I created a new GitHub repo and an app on Heroku myself, I could connect them without any issues.
We had the same problem when someone without admin access to the github repo requested the github access in Heroku. He had to revoke his access in github before we could log back into Heroku with an account that had admin access in github and properly connect the accounts.