惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Simon Willison's Weblog
Simon Willison's Weblog
Help Net Security
Help Net Security
P
Privacy International News Feed
T
Threat Research - Cisco Blogs
C
Cisco Blogs
C
CERT Recently Published Vulnerability Notes
NISL@THU
NISL@THU
L
LINUX DO - 热门话题
Security Latest
Security Latest
A
Arctic Wolf
G
GRAHAM CLULEY
月光博客
月光博客
S
Securelist
D
Docker
J
Java Code Geeks
T
Troy Hunt's Blog
T
Tenable Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
SecWiki News
SecWiki News
S
Security @ Cisco Blogs
量子位
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
L
LINUX DO - 最新话题
Recent Commits to openclaw:main
Recent Commits to openclaw:main
aimingoo的专栏
aimingoo的专栏
博客园 - 【当耐特】
H
Heimdal Security Blog
The Hacker News
The Hacker News
博客园 - 三生石上(FineUI控件)
Application and Cybersecurity Blog
Application and Cybersecurity Blog
N
Netflix TechBlog - Medium
Vercel News
Vercel News
Forbes - Security
Forbes - Security
B
Blog RSS Feed
H
Hackread – Cybersecurity News, Data Breaches, AI and More
IT之家
IT之家
B
Blog
MongoDB | Blog
MongoDB | Blog
博客园 - 聂微东
Google DeepMind News
Google DeepMind News
S
Secure Thoughts
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
C
Check Point Blog
云风的 BLOG
云风的 BLOG
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
T
The Blog of Author Tim Ferriss
L
Lohrmann on Cybersecurity
F
Full Disclosure
D
Darknet – Hacking Tools, Hacker News & Cyber Security
P
Proofpoint News Feed

LangChain Forum - Topics tagged langsmith-studio

Unable to delete runs from annotation queue Incorrect `reasoning_effort` options in the UI Unexpected latency in minimal Deep Agent setup (create_deep_agent) + confusing @traceable runs LangSmith Studio file upload with Deep Agents causing OpenAI 400 error Why can't my 'langgraph cli' load 'checkpointer' TypeError: Type is not JSON serializable: ProxyUser Langsmith Stream Issues How to use another model in the langsmith Agent Builder UI? # [Bug/Question] Runtime Context Not Working in Deployed LangSmith Agent - Headers and Config Stripped Alert notifications not triggering for tag-based Parallel Test Scenarios vs OpenAI Rate Limits Unplanned triggering of “PII detection” when launching the agent in self-hosted LangSmith Studio can't connect to self-hosted LangGraph server on Railway - "origin is not allowed" POSTGRES_URI_CUSTOM is ignored by LangGraph runtime; runtime always falls back to in-memory Langsmith Studio not showing state schema Image registration issue Manager graph does not get the header despite adding the custom heade in langgraph.json Feedback request: LangGraph + Laravel workflow to auto-fill form fields from a PDF diagram Local server setup failed LangGraph CLI treats InjectedState as required tool parameter and fails the validation Support passing runtime context in Send API InvalidUpdateError: Node __copy__ does not exist - LangGraph State Update Failure Does langGraph-studio not support user custom type? How to get the Original Tool Call Output in the agent? How to Pass Runtime Data from SDK to LangGraph Nodes Without Polluting State? Question: Custom datasets inside LangGraph platform DBs How can I properly integrate open-deep-research package to my existing backend? Studio not recognizing my custom inputs How do I view the state of a subgraph with a persistent sub-thread? [Bug Fix Announcement] Studio Experiments having empty results Post Identification and Tags
"Error: No assistants found." in LangGraph Studio platform when LG Server authorization is enabled in langgraph.json
2025-08-06 · via LangChain Forum - Topics tagged langsmith-studio

1

Hey,

When I enable authorization in langgraph.json in the following way:
“auth”: {
“path”: “src/security/auth.py:auth”
},

where the security script simply checks “Authorization: Bearer ” (token must be equal to some env var)
I can’t access LangGraph Studio. Following message is displayed:
Error: No assistants found.

When I hit a “Deloyment Settings” cog-wheel next to the “Studio” button and set up an Authorization header with a value “Bearer ” the above message changes to:
Error: Failed to fetch assistants: . Forbidden

The token is 100% correct – the deployment works with curl commands

2

I found a solution – you need to add special handling for a Studio user:

1 Like