Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Mateusz Kurek
@mkurek
in other words, read serialization is different than write serialization
Pete
@kasim1r
would you mind posting a dump of your (working) LDAP settings?
Pete
@kasim1r
please?
✪ vi4m Marcin Kliks
@vi4m
any problems with ldap?
Pete
@kasim1r
ldap.FILTER_ERROR: {'desc': 'Bad search filter'}
on ldap_sync
just like the guy in the issue
✪ vi4m Marcin Kliks
@vi4m
@ar4s will help you with it
Pete
@kasim1r
and nobody posted an actual solution
cool
Arkadiusz Adamski
@ar4s
@kasim1r we have something like this https://gist.github.com/ar4s/6ec50eb60e125bfd17a2d6961a1db7e0
Pete
@kasim1r
wow ok, i will try to adapt that to my stuff
thanks, mate
Arkadiusz Adamski
@ar4s
BTW I'm not expert of LDAP but I do my best :smile:
Please also note that variable AUTH_LDAP_USER_FILTER starts with (|( and ends with ))
Pete
@kasim1r
you guys are not mapping anyone to "staff"?
Arkadiusz Adamski
@ar4s
https://github.com/allegro/ralph/blob/ng/src/ralph/accounts/ldap.py#L23-L28
if user is active then is staff
Pete
@kasim1r
aha, great
Pete
@kasim1r
ok, that did work without errors
I even see group mappings, just no users were imported
or will the ralp user accounts be generated when they first log in?
*ralph
I already saw that with one other person, the account was auto-generated when they logged in with their AD credentials, but I had to manually tick the "staff" and "active" options in the user account
Pete
@kasim1r
tried with a test user now. his account got auto-generated, but not "active", not "staff"
Arkadiusz Adamski
@ar4s
maybe try
AUTH_LDAP_USER_FLAGS_BY_GROUP = { "is_active": "cn=active,ou=groups,dc=example,dc=com", "is_staff": ["cn=staff,ou=groups,dc=example,dc=com", "cn=admin,ou=groups,dc=example,dc=com"], "is_superuser": "cn=superuser,ou=groups,dc=example,dc=com" }
Pete
@kasim1r
okay
ivanususu
@ivanususu
can someone tell me how to swap the rack around? RU1 to be on top and RU46 on bottom?
Pete
@kasim1r
OK, nesting obivously only works for "normal" ralph groups, f.e. "Support" or "Admins"
not for AUTH_LDAP_GROUP_MAPPINGor AUTH_LDAP_USER_FLAGS_BY_GROUP
Pete
@kasim1r
which in turn means, I cannot make it so that people who log in are automatically "active" and "staff" tagged
Mateusz Kurek
@mkurek
@kasim1r ralph handles it for you: https://github.com/allegro/ralph/blob/ng/src/ralph/accounts/ldap.py#L27
@ivanususu it's not possible at the moment. and why do you want to do that?
ivanususu
@ivanususu
@mkurek well, because our rack layout is like that
Pete
@kasim1r
well, just take your label printer and renumber the height units :)
Mateusz Kurek
@mkurek
do you want to do this for all your racks or selected ones?
ivanususu
@ivanususu
for all racks
Pete
@kasim1r
jeez, sorry.
damian1976
@damian1976
This message was deleted
Mateusz Kurek
@mkurek
@ar4s any idea for @ivanususu issue? :)
Pete
@kasim1r
@ivanususu doesn't the "orientation" field do what you need?
ivanususu
@ivanususu
@kasim1r nope, that's just for the text in the small squares
Pete
@kasim1r
ah, too bad.
Arkadiusz Adamski
@ar4s
@ivanususu allegro/ralph#2832
@ivanususu do you mean something like this?
https://cloud.githubusercontent.com/assets/351535/19113520/4d49d5d4-8b0a-11e6-9d23-afa334d64a03.png
Pete
@kasim1r
probably, configurable per rack methinks
ivanususu
@ivanususu
@ar4s yes! thank you
Arkadiusz Adamski
@ar4s
Great. After we merge this allegro/ralph#2832 please update your codebase and add RACK_LISTING_ORDER_REVERSE = True to your settings.
Pete
@kasim1r
@ar4s do you see the message I sent you?