We have a secured enterprise gateway that requires auth via an OIDC callback (auth-code + PKCE) —
no static token, no Entra→gateway exchange.
Claude Desktop handles this today with inferenceCredentialKind: "interactive" + inferenceGatewayOidc and the user signs into the gateway's IdP and we get a per-user token directly (important for usage and quotas).
The Office add-in has no equivalent, only entra_sso + bootstrap_url, which doesn't work when the gateway is its own OAuth server. Can the add-in support the same interactive OIDC sign-in as Desktop (redirect-based)? That's the only clean path to per-user auth for gateways like urs. I have seen other issues (#179) where people spin up a multipass auth servers just for that so we are not the only use case.
We have a secured enterprise gateway that requires auth via an OIDC callback (auth-code + PKCE) —
no static token, no Entra→gateway exchange.
Claude Desktop handles this today with
inferenceCredentialKind: "interactive"+inferenceGatewayOidcand the user signs into the gateway's IdP and we get a per-user token directly (important for usage and quotas).The Office add-in has no equivalent, only
entra_sso+bootstrap_url, which doesn't work when the gateway is its own OAuth server. Can the add-in support the same interactive OIDC sign-in as Desktop (redirect-based)? That's the only clean path to per-user auth for gateways like urs. I have seen other issues (#179) where people spin up a multipass auth servers just for that so we are not the only use case.