You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
integriq presents itself to the credential broker as 'openconnector', so allowedApps ['integriq'] is refused with 403Β #2435
A credential minted for integriq with allowedApps: ["integriq"] is refused on every brokered call:
403 Credential broker refused the request (Request not permitted). If Integriq should be allowed to use this credential, add β¦
nextcloud.log: [CredentialBrokerService] request denied: app "openconnector" not in allowedApps.
integriq presents itself to OpenRegister's credential broker as openconnector, the old app id. An administrator who follows the error message and allows integriq gets the same 403 again. Allowing openconnector fixes it, and nothing in the UI, the docs or the error says so.
Reproduce
OpenRegister + integriq on one instance; the github-api source from lib/Settings/register.d/github-source.json with credentialRef.credentialName: github-publiccode.
POST /apps/openregister/api/credentials with {"name":"github-publiccode","provider":"github","secret":"β¦","allowedApps":["integriq"]}.
Run a flow with openconnector.source-paginate on that source β 24Γ 403, run "completed" with 0 items.
PUT /apps/openregister/api/credentials/{id} with {"allowedApps":["integriq","openconnector"]} β calls succeed.
Measured 2026-10-01 on integriq 0.4.10-unstable.20261001075532, openregister 2.1.34-unstable.20261001080921.
Fix options
BrokeredCallService (or wherever the app id is set on the broker request) sends integriq.
During the transition, OpenRegister's broker could accept openconnector as an alias for integriq, or integriq's error message could name the id it actually uses.
The seeded github-api source (and the catalogue entry) could say which app id must be in allowedApps.
Activity
github-actions commentedon Oct 1, 2026
Thank you for opening this issue! It has been assigned to @rubenvdlinde for review.
What happens next:
Triage labels:
triage:accept-featureβ accepted as a new featuretriage:accept-bugfixβ accepted as a bug fixtriage:needs-infoβ more information neededtriage:wontfixβ will not be addressedtriage:duplicateβ duplicate of another issue