[GH-ISSUE #118] Cannot pass per-source token for GitHub or GitLab #71

Closed
opened 2026-10-18 21:14:05 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @Fyrlex on GitHub (Sep 11, 2026).
Original GitHub issue: https://github.com/open-webui/oikb/issues/118

Only GITHUB_TOKEN and GITLAB_TOKEN can be used for their respective sources, preventing per-source authentication tokens.

GitHub and GitLab have token params in their constructors, but no tokens are passed to them in the cli.py file.

A fix would be to extract the token from the oikb.yaml source entries and pass it to the _resolve_connector function so it can be passed to the GitHub and GitLab connectors.

Originally created by @Fyrlex on GitHub (Sep 11, 2026). Original GitHub issue: https://github.com/open-webui/oikb/issues/118 Only GITHUB_TOKEN and GITLAB_TOKEN can be used for their respective sources, preventing per-source authentication tokens. GitHub and GitLab have token params in their constructors, but no tokens are passed to them in the cli.py file. A fix would be to extract the token from the oikb.yaml source entries and pass it to the _resolve_connector function so it can be passed to the GitHub and GitLab connectors.
Author
Owner

@Fyrlex commented on GitHub (Sep 11, 2026):

Seems that this is an issue with SharePoint too. The resolve connector is based on the source.startswith() to determine the proper class to use, but the classes are built to accept more params that the resolver does not provide. More specifically, the connector resolver only tkaes a few params to identify the path, but not authentication methods like the SharePoint client id, secret, and tenant.

Perhaps the resolver needs to be remade or be optimally designed to also pass all kinds of authentication methods.

<!-- gh-comment-id:5641495030 --> @Fyrlex commented on GitHub (Sep 11, 2026): Seems that this is an issue with SharePoint too. The resolve connector is based on the source.startswith() to determine the proper class to use, but the classes are built to accept more params that the resolver does not provide. More specifically, the connector resolver only tkaes a few params to identify the path, but not authentication methods like the SharePoint client id, secret, and tenant. Perhaps the resolver needs to be remade or be optimally designed to also pass all kinds of authentication methods.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/oikb#71
No description provided.