feat: enterprise OIDC, APIM client credentials, Azure discovery, scientific workbench - #291
Open
MChorfa wants to merge 1 commit into
Open
feat: enterprise OIDC, APIM client credentials, Azure discovery, scientific workbench#291MChorfa wants to merge 1 commit into
MChorfa wants to merge 1 commit into
Conversation
…ntific workbench Syncs the enterprise-oidc-foundry branch with the latest dev and squashes 121 commits into one. Resolves conflicts in the sidebar navigation (dev replaced the Workbench row with a New task action; our Science tab is retained), the goal extension (dev moved injection in-process; our branding is kept on the pure section builder), and the agent-runtime extension list (dev added automations and removed the goal extension path; our notebooks and FastCRW search extensions are retained). Includes all enterprise OIDC, APIM client credentials, Azure-style model discovery, scientific workbench, SPIFFE workload identity, foundry APIM governance, provisioning coordinator, and cortAIx appliance features.
MChorfa
force-pushed
the
feat/enterprise-oidc-foundry
branch
from
July 30, 2026 14:07
500c9d6 to
13cab15
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apim_client) provider authentication with token exchange, subscription key support, and secret storage as references (never leaked in responses)providerModelsEndpoint— uses/openai/deployments?api-version=for Azure path-style providers,/v1/modelsfor OpenAIapim_clientpresets: hybrid preset defaults + operator overrides for issuer_id, client_id, client_secret, token_endpoint, audience, scopes, path_style, api_versionTest plan
npm run check— frontend quality gate (lint, typecheck, tests, build) + controller typecheck/lint/testnpm run test:integration— agent-runtime tests, enterprise OIDC/session integration, provider-routing integration, foundry routes, provider securityproviderModelsEndpoint(Azure + OpenAI paths) anddiscoverProviderModelswith Azure path_styleapim_clientprobe + create flow with mock token server, verifyingclient_secretis stored as a reference and not leaked