Expired50% confidenceFactExact time
OpenAI's Session Token is typically named __Secure-next-auth.session-token, with HttpOnly and Secure flags set to prevent direct reading by JavaScript and transmission over non-HTTPS connections.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
7/6/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 10/4/2026(expired)
Sources
Related Claims
Unverified使用API中转平台时，OpenAI的服务条款与隐私政策对用户数据的保护完全失效，因为服务器的通信对端始终是中转平台68% similarUnverifiediLink creates a unique OpenID and AccessToken for each session authorized by QR code scanning; tokens have a limited validity period and must be refreshed periodically.67% similarUnverified使用第三方代理密钥时，OpenAI服务端只能识别到平台账户的访问行为，无法追踪到最终用户66% similarUnverified中转站对外暴露的接口完全兼容OpenAI官方规范，用户侧代码几乎无需修改，仅替换Base URL和API Key即可切换66% similarUnverifiedFor user login scenarios in web applications, the Authorization Code mode of OAuth 2.0 is the safest and most recommended choice, as it exchanges tokens through a backend server, avoiding exposing sensitive credentials to the browser.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/112602API
curl https://kongchang.com/api/v1/knowledge/claims/112602MCP
get_claim(id=112602)