Which product's docs own a given top-level frodo capability domain (the
frodo.<domain>... namespace, e.g. 'realm', 'idm', 'authn'):
'am' / 'idm': operations under this domain call that component's API
exclusively (verified against the actual generateAmApi/generateIdmApi
call sites, not inferred from the domain's name — several domain names
are misleading, e.g. user is AM's identity-store users REST resource,
not IDM managed users, which live under idm.managed instead).
'both': the domain spans both components (e.g. whole-tenant config
export/import), so a single product can't be chosen for it.
'cloud-only': an Advanced Identity Cloud SaaS feature with no ForgeOps
equivalent at all (ESVs, IGA, promotion, service accounts, ...).
'n/a': an internal/client-side helper with no corresponding product
documentation (HTTP client factory, local utility functions, connection
profile and token cache management).
Which product's docs own a given top-level frodo capability domain (the
frodo.<domain>...namespace, e.g.'realm','idm','authn'):'am'/'idm': operations under this domain call that component's API exclusively (verified against the actualgenerateAmApi/generateIdmApicall sites, not inferred from the domain's name — several domain names are misleading, e.g.useris AM's identity-store users REST resource, not IDM managed users, which live underidm.managedinstead).'both': the domain spans both components (e.g. whole-tenant config export/import), so a single product can't be chosen for it.'cloud-only': an Advanced Identity Cloud SaaS feature with no ForgeOps equivalent at all (ESVs, IGA, promotion, service accounts, ...).'n/a': an internal/client-side helper with no corresponding product documentation (HTTP client factory, local utility functions, connection profile and token cache management).