RootDNAccessControlPlugin has set_open_time() and set_close_time() methods, but they can't be used because these plugin attributes should be set together. If I try to use just set_open_time(), server returns err=53, in the errors log:
RootDNAccessControlPlugin
set_open_time()
set_close_time()
[24/May/2019:09:24:36.526222533 -0400] - ERR - rootdn-access-control-plugin - rootdn_load_config - There must be a open and a close time. Ignoring time based settings. [24/May/2019:09:24:36.529887291 -0400] - ERR - rootdn-access-control-plugin - rootdn_init - Unable to load plug-in configuration [24/May/2019:09:24:36.532256982 -0400] - ERR - plugin_setup - Init function "rootdn_init" for "RootDN Access Control" plugin in library "librootdn-access-plugin" failed [24/May/2019:09:24:36.535201439 -0400] - ERR - plugin_restart - Plugin (cn=RootDN Access Control,cn=plugins,cn=config) failed to restart after configuration change (Init function "rootdn_init" for "RootDN Access Control" plugin in library "librootdn-access-plugin" failed.). Reverting to original plugin entry. [24/May/2019:09:24:36.538228204 -0400] - ERR - dse_pre_modify_plugin - The configuration change for plugin (cn=RootDN Access Control,cn=plugins,cn=config) could not be applied.
Impacts CLI tools as well
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.0
CLI uses direct set attribute approach. But I agree, we should add an additional check in the CLI/UI that both open and close times are specified if any.
set
Metadata Update from @mreynolds: - Issue priority set to: major - Issue set to the milestone: 1.4.1 (was: 1.4.0)
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.3 (was: 1.4.1)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3463
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)