- Shipped
- 4 செப்டம்பர், 2026 அன்று 12:31 AM UTC
- Author
- Kamo
- Commit
- 3eb7d0b
A white-label sign-in screen is reached at login.<customer domain> with no ?org= on the URL and nothing in sessionStorage, so the front end has no way to name the organization whose logo and colours it must paint. It fell back to deriving a theme folder from the hostname, which only ever answers for organizations that predate the alias migration. /org/public/by-host/{host} resolves it properly: OrgResolutionService.byHost, the same rule the sign-in host uses, returning the alias the theme folder is actually named for. Read-only on purpose — the sibling /org/domain/{fqdn} auto-provisions app features as a side effect, and an unauthenticated endpoint reachable by putting any hostname in a URL must not write. careers joins KnownAliases, SSL_PROBE_LABELS and the reserved alias list: byHost reads a leading label that is not a known platform alias as an organization's own alias, so careers.<domain> resolved as "the org aliased careers" until DomainAliasType.CAREERS landed (shared-lib b692cfc4).