sergehuber opened a new pull request, #935: URL: https://github.com/apache/unomi/pull/935
## Summary - JAAS admin requests without `X-Unomi-Tenant-Id` use `admin.default.tenant.id` (default `default`), so 3.0 scripts keep seeing migrated data. - Unknown tenant / missing default → HTTP 400 after auth; wrong credentials stay HTTP 401 either way. - `X-Unomi-Tenant-Id: system` is required for the system context, and only `ROLE_UNOMI_ADMIN` may use it. - Same rules on REST (`/cxs/*` and `/cxs/tenants`) and GraphQL; docs and migration examples updated. https://issues.apache.org/jira/browse/UNOMI-1008 ## Test plan - [x] `mvn -pl api,rest,graphql/cxs-impl -am test -Dtest=AdminTenantSelectionTest,AuthenticationFilterAdminTenantTest,AuthenticationFilterBlankPasswordTest,GraphQLServletSecurityValidatorTest -Dsurefire.failIfNoSpecifiedTests=false` - [ ] Manual: after migration, JAAS call without header sees `default` tenant data; unknown header → 400; `X-Unomi-Tenant-Id: system` as full admin works -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
