You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

使用ADAL调用Yammer REST API时出现502 Bad Gateway错误求助

Troubleshooting 502 Bad Gateway (nginx) on Yammer my_feed.json API

Hey there, let's break down this issue you're facing with the Yammer REST API. First, let's recap the key details to make sure I'm aligned with your scenario:

Starting last Thursday, you're getting consistent 502 Bad Gateway (nginx) responses when calling the https://www.yammer.com/api/v1/messages/my_feed.json endpoint. You're using ADAL for token acquisition, your Azure AD apps have user impersonation permissions, no code changes were made, and multiple apps are affected.

Likely Causes & Actionable Next Steps

  • Preview Feature Instability
    Since the user impersonation permission is in preview, this is the most probable culprit. Preview features often have unplanned backend adjustments or temporary outages that can break existing integrations. I'd first check Yammer's official service status dashboard (look for API-specific incidents) to see if there's a known outage affecting the my_feed.json endpoint.

  • Azure AD-Yammer Integration Drift
    Even without code changes, backend configurations can shift silently. Try these quick validation steps:

    • Double-check that the user impersonation permission is still enabled and properly configured for all affected Azure AD apps—sometimes preview permissions get revoked or adjusted without notice.
    • Generate a fresh test token via ADAL and use a tool like Postman to call the endpoint directly. This rules out any hidden token-handling issues in your code (unlikely since multiple apps are affected, but worth confirming quickly).
  • Yammer Frontend Gateway Glitch
    The 502 response comes from nginx, pointing to a problem with Yammer's entry-level gateway layer. If the service status page shows no issues, you could try experimenting with alternative endpoints (like Yammer's v2 API equivalents, if available) to see if they bypass the problematic gateway.

If none of these steps resolve the issue, I'd recommend reaching out to Azure Support or the Yammer Developer Community with a detailed ticket—include the timeline, number of affected apps, and the preview permission type to help the team prioritize your case.

内容的提问来源于stack exchange,提问作者user2375291

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.25 04:10:10