[Pki-devel] ProfileSubsystem configuration with LDAPConnection

[Fraser Tweedale]

With the introduction of LDAP-based profiles, the ProfileSubsystem
needs access to the profile configuration.  When spawning a new
instance, the CMS tries to start its subsystems, but the
ProfileSubsystem cannot start because it requires the LDAP
connection details, which are not yet configured (this action is
performed by SystemConfigService.configureDatabase).

OK, so what to do?  I see two options:

1) Remove the profile subsystem from the initial CS.cfg, so that it
doesn't start up.  Add it back into CS.cfg as a configuration step;
on the next startup, it will run and be happy, because the database
configuration is there.

2) Handle the absense of database configuration in ProfileSubsystem
itself.  That is, keep track of whether initialisation has been
successfully performed, and try again "just-in-time" when it is
needed.  This probably violates semantics of the IProfileSubsystem
API.

Feedback or other ideas are appreciated.  I'm going to push ahead
with option (1).  Both options feel like hacks but (2) seems like a
worse hack ^_^

Cheers,

Fraser