elsa-workflows / elsa-workflows/elsa-core

[BUG] CustomTenantAccessor causes Http Endpoint 404 in elsa 2.14 #2861

Open
#5,932 2 comments 0 reactions 0 assignees View on GitHub
bug triaged
Dominant language
C#
Stars
7.9k
Forks
1.5k
Avg merge
15h 22m
Merged PRs (30d)
114

Description

## Description
I Add CustomTenantAccessor to use multi tenant in elsa 2.14.1 . It work with Tenant . But when I call to endpoint , it return 404 (just work with tenantId is null)

![image](https://github.com/user-attachments/assets/2f371260-d365-4e8f-a362-bf85fddef0be)
![image](https://github.com/user-attachments/assets/011ab08c-5725-413d-8c70-48b80de75543)
![image](https://github.com/user-attachments/assets/4a7ae5c1-01be-4dd9-b179-f2c69d76c89e)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported Elsa 2.14.1 scenario with a CustomTenantAccessor and an HTTP endpoint, comparing requests with a tenantId and with a null tenantId. Trace tenant resolution and endpoint matching to identify why the tenant-specific request returns 404; done means the endpoint works for a configured tenant as well as when tenantId is null.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
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.