Page tree
Skip to end of metadata
Go to start of metadata

Proposal

COmanage should drop support for Pooled Organizational Identities.

Benefits

  1. There is a significant amount of complex logic for handling both pooled and unpooled deployments. Dropping support will allow for removal of this code and simplify maintenance of the codebase.
  2. Some registry capabilities (such as Extended Types) do not support pooled organizational identities. Removing the capability makes for a more consistent feature set.
  3. Removing this option will simplify deployment for new adopters.

Drawbacks

  1. There will be no easy way to share organizational identities across COs. Each CO will require its own copy of each organizational identity.

Conclusion

(tick) Accepted

Organizational Identity Pooling is mostly a historical feature that is no longer required. Originally, all organizational identities were pooled, however this led to problems in multitenant deployments. In newer deployments, the requirement for permeability of organizational identities across boundaries can instead be met with use of COUs.

  • No labels