Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configure SASL/GSSAPI/Kerberos without server restart #790

Closed
389-ds-bot opened this issue Sep 12, 2020 · 10 comments
Closed

configure SASL/GSSAPI/Kerberos without server restart #790

389-ds-bot opened this issue Sep 12, 2020 · 10 comments
Labels
closed: fixed Migration flag - Issue

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47453


configure all server related SASL/GSSAPI/Kerberos related settings without restart - including setting a keytab to use until the next restart - the goal is to be able to set up a directory server to be a SASL/GSSAPI/Kerberos server, and to use server to server SASL/GSSAPI without having to restart - and to configure any other related settings without a restart

@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 12, 2020
@389-ds-bot 389-ds-bot added this to the 1.3.3 - 1/14 (January) milestone Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2014-02-18 01:07:24

Your patch looks good to me.

I have one request -- logging the successfully set var, value pairs in the error log. The TASK_SYSCONFIG_FILE_ATTR file could be manually updated any time and we could lose what values are currently set. We could add getenv task. But I guess that's an overkill... ;)

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2014-02-18 04:04:33

Replying to [comment:5 nhosoi]:

Your patch looks good to me.

I have one request -- logging the successfully set var, value pairs in the error log.

Any particular log level (TRACE or CONFIG), or default logging? I don't know if we should log it by default though.

The TASK_SYSCONFIG_FILE_ATTR file could be manually updated any time and we could lose what values are > currently set. We could add getenv task. But I guess that's an overkill... ;)

I'm not sure what you are concerned about here. Could you elaborate please? Thanks!

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2014-02-18 20:29:03

Replying to [comment:5 nhosoi]:

Your patch looks good to me.

I have one request -- logging the successfully set var, value pairs in the error log. The TASK_SYSCONFIG_FILE_ATTR file could be manually updated any time and we could lose what values are currently set. We could add getenv task. But I guess that's an overkill... ;)

I added a new attribute to say if the changes should be logged or not. I do have a check that if setenv fails, it reports an error and quits. So there is no need to do a getenv after the setenv.

New patch attached.

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2014-02-18 21:39:37

A user could add an environment variable of the form

export FOO=bar

to /etc/sysconfig/dirsrv or /etc/sysconfig/dirsrv-INSTANCE. In a sysvinit/service system, these files can be parsed as bash.

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2014-02-18 23:39:48

Replying to [comment:8 richm]:

A user could add an environment variable of the form

export FOO=bar

to /etc/sysconfig/dirsrv or /etc/sysconfig/dirsrv-INSTANCE. In a sysvinit/service system, these files can be parsed as bash.

Added support for:

VARIABLE=value
export VARIABLE=value
setenv VARIABLE value
unsetenv VARIABLE

New patch attached.

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2014-02-19 00:05:14

Replying to [comment:9 mreynolds389]:

Replying to [comment:8 richm]:

A user could add an environment variable of the form

export FOO=bar

to /etc/sysconfig/dirsrv or /etc/sysconfig/dirsrv-INSTANCE. In a sysvinit/service system, these files can be parsed as bash.

Added support for:

VARIABLE=value
export VARIABLE=value
setenv VARIABLE value
unsetenv VARIABLE

New patch attached.

I need to add support of "set" and "unset", new patch will be attached shortly...

@389-ds-bot
Copy link
Author

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2014-02-19 00:54:34

Replying to [comment:10 mreynolds389]:

Replying to [comment:9 mreynolds389]:

Replying to [comment:8 richm]:

A user could add an environment variable of the form

export FOO=bar

to /etc/sysconfig/dirsrv or /etc/sysconfig/dirsrv-INSTANCE. In a sysvinit/service system, these files can be parsed as bash.

Added support for:

VARIABLE=value
export VARIABLE=value
setenv VARIABLE value
unsetenv VARIABLE

New patch attached.

I need to add support of "set" and "unset", new patch will be attached shortly...

New patch is attached...

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2014-02-19 02:00:48

git merge ticket47453
Updating bb4f0c4..681be0d
Fast-forward
ldap/servers/slapd/task.c | 192 +++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 192 insertions(+), 0 deletions(-)

git push origin master
bb4f0c4..681be0d master -> master

commit 681be0d
Author: Mark Reynolds mreynolds389@redhat.com
Date: Tue Feb 18 13:52:19 2014 -0500

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-02-11 23:04:06

Metadata Update from @mreynolds389:

  • Issue assigned to mreynolds389
  • Issue set to the milestone: 1.3.3 - 1/14 (January)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: fixed Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant