12 Commits

Author	SHA1	Message	Date
Michael Friedrich	b7f923dd01	'api setup' must not override existing certificate and api-users.conf file ... fixes #10560	2015-11-08 14:19:06 +01:00
Michael Friedrich	1c8531fc0d	Fix: 'api setup' should create a user even when api feature is already enabled ... fixes #10560	2015-11-08 14:06:36 +01:00
Gunnar Beutner	12015e0eca	Clean up the 'api setup' command a bit more ... refs #9471	2015-10-26 07:03:41 +01:00
Gunnar Beutner	b72ba2b63a	Fix incorrect return value for ApiSetupUtility::SetupMaster ... refs #9471	2015-10-25 19:57:57 +01:00
Gunnar Beutner	f31837a6ba	Clean up the 'api setup' command ... refs #9471	2015-10-22 16:03:26 +02:00
Gunnar Beutner	425a1a0166	Implement API permissions ... fixes #9088	2015-09-28 14:30:46 +02:00
Michael Friedrich	7eca257784	Fix return value of Utility::MkDir/MkDirP ... None as there are exceptions thrown. fixes #9689	2015-08-24 15:11:49 +02:00
Michael Friedrich	f123c8218d	Split ApiSetupUtility::SetupMaster() into multiple functions ... refs #9590	2015-07-08 15:32:11 +02:00
Michael Friedrich	2eaae1f733	Update documentation for ApiUser object & node wizard ... fixes #9471	2015-06-25 18:03:00 +02:00
Michael Friedrich	0d977b9d48	Allow to pass cn to ApiSetupUtility::SetupMaster() ... refs #9471	2015-06-25 10:40:50 +02:00
Michael Friedrich	663f09e475	Only run 'api setup' if the feature was not enabled ... It is safe to assume that the user either did run 'node wizard' or 'node setup' in >= 2.3.x before, or manually enabled the api feature and deployed the certificates (otherwise Icinga2 wouldn't start either). In that case we'll skip the api setup to ensure that we don't override any existing configuration at all. refs #9471	2015-06-25 10:21:18 +02:00
Michael Friedrich	7b0b04ba8f	Implement 'api setup' cli command & add ApiUser config ... refs #9471	2015-06-25 10:08:34 +02:00