Skip to content
This repository has been archived by the owner on Aug 12, 2024. It is now read-only.

Support more authentication options #739

Open
varshaprasad96 opened this issue Oct 11, 2023 · 2 comments
Open

Support more authentication options #739

varshaprasad96 opened this issue Oct 11, 2023 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@varshaprasad96
Copy link
Member

At present, rukpak exclusively supports SSH-based authentication, as indicated in the code here:

// For the ssh authorization of the GitSource, the secret is expected to contain `data.ssh-privatekey` and `data.ssh-knownhosts` for the ssh privatekey and the host entry in the known_hosts file respectively.
. However, this limitation may prove restrictive, particularly for scenarios that require Git-based authentication. Expanding rukpak's capabilities to encompass a broader spectrum of authentication methods, such as Kerberos, JWT, OAuth, would be helpful.

@varshaprasad96 varshaprasad96 changed the title Handle more authentication options Support more authentication options Oct 11, 2023
@fgiloux
Copy link
Contributor

fgiloux commented Oct 12, 2023

Do you want to cover container registry authentication with this issue or create a separate one for it? This is often done with a kubernetes.io/dockerconfigjson secret.

Copy link

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants