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

LDAP Sync TODO list #4851

Open
22 of 27 tasks
stevekuznetsov opened this issue Sep 29, 2015 · 23 comments
Open
22 of 27 tasks

LDAP Sync TODO list #4851

stevekuznetsov opened this issue Sep 29, 2015 · 23 comments
Labels
component/auth help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2

Comments

@stevekuznetsov
Copy link
Contributor

stevekuznetsov commented Sep 29, 2015

Dev-cut:



Post dev-cut:

@deads2k
Copy link
Contributor

deads2k commented Oct 5, 2015

@stevekuznetsov Schema1 works with an exposed config. Once you get enough tests done for it, we can claim the trello card.

@deads2k
Copy link
Contributor

deads2k commented Oct 6, 2015

"install openldap client" - openshift/vagrant-openshift#336

@deads2k
Copy link
Contributor

deads2k commented Oct 9, 2015

Need union group name mappings to allow user-defined if present and attributes otherwise.

Also, we need to make a label of the hostname on groups we sync. Its not perfect, but its better than nothing.

We also need to add a custom --label flag to add custom labels.

@stevekuznetsov
Copy link
Contributor Author

We need to find a way to mutate the host to be a label, previously there was the issue of formatting (labels can't have colons? I can't remember).

@deads2k
Copy link
Contributor

deads2k commented Oct 11, 2015

We need to find a way to mutate the host to be a label, previously there was the issue of formatting (labels can't have colons? I can't remember).

Yeah, we couldn't do host:port, but we need some kind of selector. We'll do host by default (which should work) and we'll leave custom labels for people doing crazy things.

@lypht
Copy link

lypht commented Jan 6, 2016

Happy New Year, all! Is there a branch that is in sync with the Openshift Origin documentation? Running oadm groups sync --type=openshift --sync-config=foo.yml as per these instructions throws unknown command: sync and unknown flag: --type errors respectively. We have validated that the command fails on both a libvirt bin/cluster development build and a GCE BYO stack, both built from openshift/openshift-ansible.

@stevekuznetsov
Copy link
Contributor Author

@lypht Current Origin HEAD is in sync with the documentation, and the last changes for this command were made in commit stevekuznetsov@6eb1b36, merged fifteen days ago. Perhaps the build is picking up an older version? Does openshift ex sync-groups work in place of oadm groups sync?

@lypht
Copy link

lypht commented Jan 6, 2016

Thanks, Steve. It looks like what is being deployed through Ansible is from December 2nd. Should I build from origin source to get these commits?

@stevekuznetsov
Copy link
Contributor Author

The version from December 2nd should have LDAP group sync, but oadm groups sync is invoked with openshift ex sync-groups, but unless you upgrade to at least December 9th (d2c5199), you won't have oadm groups prune. I'd suggest you use the latest version you can.

@lypht
Copy link

lypht commented Jan 7, 2016

Thanks again. If I run the upgrade playbook from BYO, will it pull the latest stable, or is this only for versioning if not on 1.1?

@stevekuznetsov
Copy link
Contributor Author

I'm not certain about that, @sdodson could you please chime in?

@sdodson
Copy link
Member

sdodson commented Jan 7, 2016

Thanks again. If I run the upgrade playbook from BYO, will it pull the latest stable, or is this only for versioning if not on 1.1?

The playbooks, unless you specify that you want a containerized install, rely on RPMs for installation and those are only built for tagged releases. If you like you can add containerized=true and give that a shot but it's definitely a less tested path at this point.

https://github.com/openshift/openshift-ansible/blob/master/README_CONTAINERIZED_INSTALLATION.md documents containerized installation.

@lypht
Copy link

lypht commented Jan 13, 2016

openshift ex sync-groups works. Thanks again!

@stevekuznetsov
Copy link
Contributor Author

@lypht glad to hear! Feel free to send other feedback or thoughts to me on GitHub or to our mailing list.

@pweil-
Copy link
Contributor

pweil- commented Jun 26, 2017

@stevekuznetsov
Copy link
Contributor Author

@enj you are very welcome

@stevekuznetsov stevekuznetsov assigned enj and unassigned stevekuznetsov Jun 26, 2017
@enj enj added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Oct 9, 2017
@aneagoe
Copy link

aneagoe commented Nov 13, 2017

I'm not really sure where a RFE would fit, but it's highly related to this topic.
There doesn't seem to be a way to define multiple ldap URLs and the proposed way to handle redundancy is far from ideal (https://docs.openshift.com/container-platform/3.6/install_config/advanced_ldap_configuration/sssd_for_ldap_failover.html) since it requires configuration of additional infrastructure (two additional servers, httpd as proxy, integration of said servers with ldap and clustering to move a virtual IP between). Ideally, one should just be able to specify the additional URLs in the config and have openshift failover if the first one fails. Can this be integrated into this TODO list or where should I submit such request?

@enj
Copy link
Contributor

enj commented Nov 13, 2017

@aneagoe I added it as a TODO item at the top, but you are welcome to submit an RFE to https://bugzilla.redhat.com. Any changes to LDAP are low priority and are unlikely to be addressed at this time.

@rjhowe
Copy link

rjhowe commented Nov 22, 2017

@aneagoe This was already proposed and denied keeping with the proposed way outlined in the doc link you provided. Bug/RFE 1459046

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 27, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 29, 2018
@openshift-ci-robot openshift-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 29, 2018
@stevekuznetsov
Copy link
Contributor Author

RIP 🌹

@enj enj added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Apr 26, 2018
@enj
Copy link
Contributor

enj commented Oct 16, 2019

/unassign

@stlaz @sttts @mfojtik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/auth help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2
Projects
None yet
Development

No branches or pull requests