QwenWork OAuth Connector Test

This ECS test service shows how a Teambition-like connector authorization flow is implemented for a custom H5 SaaS.

Connector Registration

client_id
qwenwork
client_name
QwenWork
client type
public client, no client_secret
PKCE
S256 required
DingTalk login
configured
manual fallback
disabled

OAuth Endpoints

  • Authorization: https://qwenwork-mcp.zhengwu.work/oauth/authorize
  • Token: https://qwenwork-mcp.zhengwu.work/oauth/token
  • UserInfo: https://qwenwork-mcp.zhengwu.work/oauth/userinfo
  • DCR: https://qwenwork-mcp.zhengwu.work/oauth/register

Redirect URI Allowlist

  • https://nango-cn-main-3uvzij.mulerun.cn/oauth/callback
  • https://nango.qwenwork.cn/oauth/callback
  • qwenwork-cn://mcp-oauth

Flow

  1. QwenWork opens /oauth/authorize with client_id=qwenwork, exact redirect_uri, state, and PKCE challenge.
  2. This service redirects the user to DingTalk scan-login when DingTalk credentials are configured.
  3. After DingTalk confirms identity, this service asks the user to approve QwenWork access.
  4. This service redirects QwenWork back with a one-time authorization code.
  5. QwenWork exchanges the code plus PKCE verifier at /oauth/token, then calls /mcp or protected sample APIs with the bearer token.

Manual Authorization Probe

This link is for protocol debugging. Replace the state and PKCE verifier in real tests.

Start OAuth Probe 
https://qwenwork-mcp.zhengwu.work/oauth/authorize?response_type=code&client_id=qwenwork&redirect_uri=qwenwork-cn%3A%2F%2Fmcp-oauth&scope=mcp%3Atest+profile+projects.read+tasks.read&state=replace-with-random-state&code_challenge=Yz13FINpx5fbMa-vmaNKBQHUH5lXnxT9kfM-Z05lW0M&code_challenge_method=S256