RE: ldap

When a user logs in for the first time, their user account is created in gitlab. You won't see them in the user list until they sign in once. From: gitlabhq@googlegroups.com On Behalf Of Giorgi Mezurnishvili Sent: Thursday, June 20, 2019 2:15 AM To: GitLab Subject: ldap hello i configured ld

Re: LDAP: 500 Internal Server Error (NoMethodError) with working gitlab-rake gitlab:ldap:check

So the _ in the provider 'ID' was the culprit. Removing that fixed all the issues. Thanks for your help, Bob On Tuesday, March 7, 2017 at 11:12:34 PM UTC-5, Drew Blessing wrote: > > Hi Bob, > > I'm on the GitLab team. Aleksey has a great suggestion - please contact > support at https://support

Re: LDAP: 500 Internal Server Error (NoMethodError) with working gitlab-rake gitlab:ldap:check

Hi Bob, I'm on the GitLab team. Aleksey has a great suggestion - please contact support at https://support.gitlab.com and we'll be happy to take a look. At a quick glance, I don't see anything obviously wrong with your configuration. My suggestion would be to completely remove or comment the

Re: LDAP: 500 Internal Server Error (NoMethodError) with working gitlab-rake gitlab:ldap:check

Understood, thanks. Since this is EE, have you considered reaching out to support? On Mar 7, 2017 9:39 PM, "Bob Jones" wrote: > So, I tried that and it did produce more verbose logging, but nothing > useful about what the LDAP problem is unfortunately. > > Bob > > On Tuesday, March 7, 2017 at 8

Re: LDAP: 500 Internal Server Error (NoMethodError) with working gitlab-rake gitlab:ldap:check

So, I tried that and it did produce more verbose logging, but nothing useful about what the LDAP problem is unfortunately. Bob On Tuesday, March 7, 2017 at 8:14:39 PM UTC-5, Aleksey Tsalolikhin wrote: > > > On Tue, Mar 7, 2017 at 12:09 PM, Bob Jones > wrote: > >> Is there a way I can turn up

Re: LDAP: 500 Internal Server Error (NoMethodError) with working gitlab-rake gitlab:ldap:check

On Tue, Mar 7, 2017 at 12:09 PM, Bob Jones wrote: > Is there a way I can turn up the gitlab logging verbosity to show me more > details about why the ldap call is failing? > Did you try How change gitlab log level? #9491 ? It's a year and a hal

Re: ldap account going through approval process ?

https://gitlab.com/gitlab-org/gitlab-ce/issues/25239 On Sunday, November 20, 2016 at 1:25:00 PM UTC-6, Aleksey Tsalolikhin wrote: > > > On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote: >> >> Hi >> >> I have ldap backend server configured and one can create gitlab account >> auto

Re: ldap account going through approval process ?

On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote: > > Hi > > I have ldap backend server configured and one can create gitlab account > automatically if the ldap account is valid. > Is it possible the auto-create still going through administrator's > approval first then auto-create

Re: ldap account going through approval process ?

Hi Aleksey On Tuesday, November 15, 2016 at 7:42:54 AM UTC-6, Aleksey Tsalolikhin wrote: > > Sorry, tj, cold you please remind me what you are trying to accomplish? > Do you want anyone with an LDAP account to be able to sign up for GitLab > without administrator involvement? > I (as gitlab a

Re: ldap account going through approval process ?

Sorry, tj, cold you please remind me what you are trying to accomplish? Do you want anyone with an LDAP account to be able to sign up for GitLab without administrator involvement? On Tue, Nov 15, 2016 at 2:43 AM, T.J. Yang wrote: > I went through a few runs of version gitlab CE since 10/15/2016

Re: ldap account going through approval process ?

I went through a few runs of version gitlab CE since 10/15/2016. Now the auto account creation is created locked mode. Administrator will need to unlock the newly created account. On Saturday, October 15, 2016 at 8:40:25 AM UTC-5, Aleksey Tsalolikhin wrote: > > Perhaps run "sudo gitlab-ctl reco

Re: ldap account going through approval process ?

Perhaps run "sudo gitlab-ctl reconfigure" ? ᐧ -- Need training on CFEngine, Git or Time Management? Email train...@verticalsysadmin.com. On Sat, Oct 15, 2016 at 12:19 AM, T.J. Yang wrote: > Thanks for the pointer to setting of block_auto_created_users. > > 1. set it to true and restart gilab

Re: ldap account going through approval process ?

Thanks for the pointer to setting of block_auto_created_users. 1. set it to true and restart gilab 8.12.6 [root@re02 ~]# grep block_auto_created_users /etc/gitlab/gitlab.rb block_auto_created_users: true # block_auto_created_users: false # gitlab_rails['omniauth_block_auto_created_users'] =

Re: ldap account going through approval process ?

I was just in my /etc/gitlab/gitlab.rb yesterday and I remember seeing a setting like that... Check block_auto_created_users in your ldap server definition. On Oct 11, 2016 1:36 PM, "T.J. Yang" wrote: > Hi > > I have ldap backend server configured and one can create gitlab account > automatic

Re: LDAP Authentication Problems

Where did you changed that feature? El lunes, 26 de mayo de 2014, 8:32:20 (UTC-6), Matthew escribió: > > *RESOLVED* > > The issue happened to be with my LDAP setup. I was using plain text > passwords, where it seems Gitlab requires (at this time) SSHA, SHA or MD5 > passwords. Changing passwords

Re: LDAP integration user_filter

Hi Bala, Tany thanks for your input, but unfortunately I cannot use the "memberOf" attribute since it's not active in our catalog :( Glad you got it working though Kind Regards Tomas Den onsdag 22 juni 2016 kl. 18:01:06 UTC+2 skrev Bala: > > Hi Tomas > > After several trial and error attempts (

Re: LDAP integration user_filter

Hi Tomas After several trial and error attempts (ooof), I got the below successfully working in our instance. Replace the blue names with appropriate value user_filter: 'memberOf=CN=*ActiveDirectoryGroupName*,OU=*value* ,OU=Groups,DC=*domainName*,DC=com' Bala On Monday, 20 June 2016 12:36:01

Re: LDAP integration user_filter

> > Forget above. > I probably need to use the "memberOf" attribute in the search filter but that one is missing in the catalog. I mean there's no "memberOf" attribute on the accounts. Only "memberUid" in the different groups. But, would it be possible to accomplish with the EE edition? -- Yo

Re: LDAP with Multiple Domains

an IT expert.  These configuration items were provided by our IT staff.  Once they provided the details, I used ldapsearch on the Gitlab server to confirm the configuration.Hope this helps.Regards,Rick-Original Message- From: Dioram Nepangue Sent: Apr 27, 2016 9:29 AM To: GitLab Cc: dnepa

Re: LDAP with Multiple Domains

May I know how did you come up with the ldap settings? I have 3 domains on one ldapserver and i want those 3 domains to be able to authenticate to gitlab using ldap. My current settings for domainA domain is like this: ldap: enabled: true servers: main: label: 'LDAP A

Re: LDAP with Multiple Domains

Yes. During one of our upgrades, we successfully implemented it. We currently have four configured domains. Thanks. Rick On April 26, 2016 4:20:43 AM EDT, Dioram Nepangue wrote: >Hey Rick, > > >Have you implemented the multiple domain in Gitlab? > > >Thanks. > > >Thanks. > >On Friday, July 2

Re: LDAP with Multiple Domains

Hey Rick, Have you implemented the multiple domain in Gitlab? Thanks. Thanks. On Friday, July 26, 2013 at 11:35:59 PM UTC+8, Rick Bywater wrote: > > I have been working to get my Gitlab authenticating via LDAP within my > company. After a bit of head scratching, I got my domain to work.

Re: LDAP database in Gitlab

Bharat Bhushan writes: > How can we use LDAP database in Gitlab ? I found the instructions at http://doc.gitlab.com/ee/administration/auth/ldap.html to be very easy to follow and helped me get things working in a matter of minutes. I'll be happy to share our LDAP config if you run into problem

Re: (LDAP) Error saving user: ["Notification email is not an email you own"]

I would like to let my user without an email address create an account an let's this temporary fake email address to allow them to change later. Le jeudi 3 mars 2016 08:23:44 UTC+1, Vincent Domingues a écrit : > > Hello, > > I'm trying to configure LDAP access but i can't find a solution to my

Re: LDAP attributes customization

I just upgraded from 7.14.3 to 8.0.1 CE, I can see that the code has the submissions to implement custom ldap attributes (previously in 7.14.3 it was missing). Anyway, despite the code now being more up-to-date the feature of mapping the users name to displayName inside ldap isn't working. Any

Re: LDAP search error: Invalid DN Syntax

Thanks, 7.9.1 does fix it! On Thursday, March 26, 2015 at 2:27:19 PM UTC-7, Markus Köberl wrote: > > On Thursday 26 March 2015 12:00:31 Reece Webb wrote: > > Just installed GitLab CE 7.9.0, trying to get AD authentication to work. > I > > receive an "Invalid DN Syntax" error when I try to login

Re: LDAP search error: Invalid DN Syntax

On Thursday 26 March 2015 12:00:31 Reece Webb wrote: > Just installed GitLab CE 7.9.0, trying to get AD authentication to work. I > receive an "Invalid DN Syntax" error when I try to login (bind user works). > It appears to be an issue dealing with commas in the DN. > > # gitlab-rake gitlab:ldap

Re: LDAP users cannot login after change their DN in LDAP

I'm having the same problem: after our Active Directory team moved a user from OU=A to OU=B, the user couldn't login anymore. I have solved this by changing the code in /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/ldap/access.rb => don't forget to do a gitlab-ctl reconfigure after chan

Re: LDAP authentication and disabling accounts

Thanks for the question. Since some time GitLab EE also checks credentials on ssh access. Since a few versions ago GitLab EE includes a periodic check for all users so that even when somebody doesn't try to login they are still removed from the projects, this is called the "Automatic Daily LDAP Syn

Re: LDAP authentication and disabling accounts

I know this is old, but I have the same question. -Justin On Friday, June 14, 2013 1:07:00 PM UTC-5, Robert Borkowski wrote: > > Hello, > > Does gitlab disable accounts when the associated LDAP/AD account is > disabled? > > The use case is a developer leaving/being fired from an organization. >

Re: LDAP login with single sign-on and auto blocking

Forgot to mention that I've tried 7.3.2 and 7.4.0. I'm using the omnibus install. Thanks. On Thursday, October 23, 2014 6:06:11 PM UTC-7, ttosttos Sa wrote: > > I'm trying to conifigure my GitLab CE install, so users can only log in > using LDAP, GitLab creates their account automatically but b

Re: LDAP sign in times out without specific error

It was a firewall issue on our side, nothing to do with GitLab. On Mon, Oct 13, 2014 at 8:32 PM, Cesar Augusto Vallenilla < vallenil...@gmail.com> wrote: > Hi, did you find the solution for this problem??? > > El sábado, 18 de enero de 2014 04:28:17 UTC-4:30, Werner Robitza escribió: > >> I've se

Re: LDAP sign in times out without specific error

Hi, did you find the solution for this problem??? El sábado, 18 de enero de 2014 04:28:17 UTC-4:30, Werner Robitza escribió: > > I've set up GitLab 6.4 on an EC2 machine. The app is running on HTTPS. I > enabled LDAP with these settings: > > ldap: > enabled: true > host: 'ldap.mycompany.c

Re: LDAP Authentication

Hey Michael, Please check this link. https://groups.google.com/forum/#!searchin/gitlabhq/vikas/gitlabhq/4Q0udNcaSxI/ Regards, Vikas On Sunday, 10 August 2014 07:01:30 UTC+10, Michael Findlay wrote: > > Hello, > > I am having some trouble configuring Gitlab to work with a AD network, the > belo

Re: LDAP was working, now stopped

Also, the error message in "/var/log/gitlab/unicorn/current" is: > 2014-06-11_13:32:09.36928 I, [2014-06-11T08:32:09.369125 #55508] INFO -- > omniauth: (ldap) Callback phase initiated. > 2014-06-11_13:32:09.37696 E, [2014-06-11T08:32:09.376608 #55508] ERROR -- > omniauth: (ldap) Authentication

Re: LDAP was working, now stopped

OK, so I moved the user back to that OU temporarily, changed it in the config file and ran "gitlab-ctl reconfigure" and now it is working again. Does that "ldap_bind_dn" have to be in the "ldap_base" or something? Thanks, --mobrien118 -- You received this message because you are subscribed to

Re: LDAP Authentication Problems

*RESOLVED* The issue happened to be with my LDAP setup. I was using plain text passwords, where it seems Gitlab requires (at this time) SSHA, SHA or MD5 passwords. Changing passwords back to SHA allowed the user accounts to authenticate. On Monday, May 26, 2014 5:10:50 PM UTC+9, Matthew wrote

Re: ldap active directory user filtering

Do you try: #uid: 'sAMAccountName' четверг, 10 апреля 2014 г., 0:19:10 UTC+4 пользователь Brett Taylor написал: > > I've got LDAP/AD authentication working, but I can't seem to get the > user_filter to work. If i use ldapsearch on the command line, i can filter > by memberOf fine: > > ldap

Re: ldap active directory user filtering

I'm trying to fix this same issue. First, I just commented out the 'uid' line, which produced an error that led me to notice that config/devise.rb does not use the 'user_filter' option, so I added that. After that, I get 'Access denied for your LDAP Account' for all users. The check script s

Re: ldap active directory user filtering

Hello, same problem here, I have add "user_filter: Gitlab.config.ldap['user_filter']," in ldap section of /home/git/gitlab/config/initializers/devise.rb file, and when I do "sudo -u git -H bundle exec rake gitlab:ldap:check RAILS_ENV=production" I see all of my ldap users. my ldap setting in gi

Re: LDAP sign in times out without specific error

Ok, I've found out that "uid=%uid" was wrong and it should've been "uid". I now get an LDAP timeout running the gitlab:check rake task. Will investigate further. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop