Multi-tenancy setup requires pseudo-tenant for requests not supporting multi-tenancy

Steps to reproduce

Note that I am not entirely sure whether this is really a bug or the system is not configured correctly. For my knowledge, however, it seems a bug and therefore I file this isse.

Steps to reproduce:
1. On you server domain.tld, configure two tenants a.domain.tld and b.domain.tld (but no default tenant)

Actual Results:
Access to the tenants works, but workflow execution will fail because there are requests that don't go to either of the tenant urls but directly to domain.tld.
For that URLs, Opencast won't be capable of determine to organization that should handle the requests resulting in log warning like:

2015-11-08 16:30:09 WARN (OrganizationFilter:113) - No organization is mapped to handle http://103.241.136.206:8080/search/dispatch
2015-11-08 16:30:09 WARN (OrganizationFilter:113) - No organization is mapped to handle http://domain.tld/caption/dispatch
2015-11-08 16:30:09 WARN (OrganizationFilter:113) - No organization is mapped to handle http://domain.tld/nop/dispatch

Expected Results:
In a multi-tenant setup, HTTP requests should either a) always refer to a specific tenant or b) a configuration option should enable requests not specific to tenants

Workaround (if any):
Configure a tenant domain.tld not accessible to the public.

Fixed and reviewed
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Unassigned

Reporter

Sven Stauber

Severity

Incorrectly Functioning Without Workaround