baidu / baidu/EasyFaaS

demo run error Invalid caller id

Open
#12 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
612
Forks
66
PR merge metrics
No merged PRs in 30d

Description

system:
Centos7 Linux kernel 5.14
Docker 20.10.7
EasyFaas tag demo1.0

error log:
```
curl -X "POST" "http://127.0.0.1:8001/v1/functions/brn:cloud:faas:bj:8f6e5a28c663957ea0452tion:testHelloWorld:1/invocations" -H 'X-easyfaas-Account-Id: df391b08c64c426a81645468c75163a5' -H 'Content-Type: application/json; charset=utf-8' -d $'{}'
{"Code":"InvalidInvokeCallerException","Cause":"owner id df391b08c64c426a81645468c75163a5 caller id ","Message":"Invalid caller id","Status":403,"Type":"User"}
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the POST request shown in the issue against the /v1/functions/.../invocations endpoint with the listed Docker and CentOS 7 environment. Trace how the X-easyfaas-Account-Id header is checked against the invocation caller, then inspect the related authentication or invocation tests if available. Done means the request authenticates consistently and no longer returns InvalidInvokeCallerException.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.