Authentication Realms
In Data Orchestrator, realms are logically separated and have completely different data partitions. This is also true in terms of authentication, as caller is always authenticated on a per-realm basis. As such, an authentication realm matches 1:1 an Data Orchestrator realm.
Superadmin APIs, such as housekeeping, are part of a different authentication realm which is defined upon cluster setup.
Authentication in Data Orchestrator
Data Orchestrator, by design, does not have a concept of per-user authentication built in. The definition of an authentication realm is a mean to verify a token's validity, that is most likely a public key.
This makes integrating Data Orchestrator with 3rd party authentication/authorization frameworks and SSOs extremely easy, as the whole logic for addressing user management is managed out of the cluster by a dedicated party. Depending on one's use case, it is possible to use either a very simple, dedicated OAuth server for each realm, or a full fledged SSO such as Keycloak which matches its authentication realms to Data Orchestrator's realms. Especially if you are aiming at the latter, make sure to read the advised best practices for authentication afterwards.