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 confi

ldap

hello i configured ldap autethication on gitlab ce but my ad users not symcing in users list someone will help me? -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: Add LDAP users before they log in

> > Thanks a lot Damien NOZAY. Is it possible to execute the same command over > command line? > Thanks in advnace -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an

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 > >

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 ther

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 <https://github.com/gitlabhq/gitlabhq/issues/9491> ? It

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

Hello all. I've been beating my head around this for a few hours now and cannot crack this issue. So here's the situation. I'm setting up an instance of GitLab EE Omnibus version 8.17.2-ee.0.el7. I have configured LDAP authentication against our AD server with the following co

Add LDAP members to groups and projects before user first login

Hi, Suppose GitLab server is configured to use LDAP (AD) user authentication. Trying to add a user to a project or group, GitLab is not searching the users in the LDAP server, but only in the local user repository apparently. If the LDAP user never logged in from LDAP, I simply can't ad

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

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 > appro

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? >

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

Re: ldap account going through approval process ?

ecreated again. >> 4.1 from userA's profile page, userA is not locked. >> >> So this setting is not working, >> >> >> On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote: >>> >>> Hi >>> >>> I have ldap backend

Re: Support for encrypted LDAP password

This will be implemented in the future? On Thursday, June 12, 2014 at 3:53:44 AM UTC-3, Sytse Sijbrandij wrote: > > You mean you want to compare hashes of the password? I don't think > that it is possible. > > Please be advised that GitLab doesn't store the LDAP passw

Re: ldap account going through approval process ?

t working, > > > 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

Re: ldap account going through approval process ?

ber 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 fi

Yet another cannot login with LDAP

in. I just don't see why I can search or users but gitlab can't. Even tried this with the gitlab AD account as a domain admin. Can I check some ldap config on the DC for anything? what does gitlab expect? Here's everything; ldapsearch from inside the container -- ldap

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 cr

ldap account going through approval process ?

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 ? tj -- You received this message because you are subscribed t

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.

Re: Support for encrypted LDAP password

Any solution? On Thursday, June 19, 2014 at 4:43:14 PM UTC-3, kevin chaves wrote: > > Also, would it be easy to obfuscate the password? I could make an attempt > at making the change. > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe

Re: Support for encrypted LDAP password

Any solution? On Wednesday, June 11, 2014 at 11:11:02 PM UTC-3, kevin chaves wrote: > > My company just started messing around with gitlab and we like it alot. > But one problem I ran into was setting up LDAP with an encrypted password. > My IT manager doesn't want to a

Re: Remove Standard Sign-In after LDAP enabled?

Yeah, good idea. On Wednesday, September 14, 2016 at 11:02:28 AM UTC-7, staceyt...@gmail.com wrote: > > Hi, > > I am using gitlab-ce-8.11.5-ce.0.el6.x86_64. > > I have enabled LDAP authentication for my GitLab Server. Also I have > disabled Sign Up of new user. However, o

Remove Standard Sign-In after LDAP enabled?

Hi, I am using gitlab-ce-8.11.5-ce.0.el6.x86_64. I have enabled LDAP authentication for my GitLab Server. Also I have disabled Sign Up of new user. However, on the Sign In page, I see both LDAP and Standard login. Is there any way to remove the Standard login? and if later I need to login

Re: How to make LDAP user as admin

On Thursday, February 26, 2015 at 1:02:14 PM UTC-6, Daniel Serodio wrote: > > To make a LDAP user an admin, you should use the Rails console like this: > > sudo gitlab-rails console > u = User.find_by_username("maneesh") > u.admin = true > u.save > exit > >

Linking to Omniauth to LDAP does not set ldap_email flag

When setting... gitlab_rails['omniauth_auto_link_ldap_user'] = true ...omniauth providers are linked to the ldap account on login with auto account creation, but the email isn't hard set on... /profile ...as it is when the account is created when logging in directly

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

LDAP integration user_filter

Hi, We are testing out gitlab-ce v8 Omnibus We have successfully integrated it to our openldap-server so ldap-users can login. Now we're trying to limit user logins to a specific ldap-group but cannot get it to work yet. According to http://docs.gitlab.com/ce/administration/auth/ldap.ht

LDAP Authentication Failure When Cloning via HTTPS

I am able to log into the WebUI just fine using LDAP credentials, but whenever I try to clone a project, those same LDAP credentials fail with the message below. I am running the following version of Git on my Windows box below and version 8.8.3 of GitLab Community Edition on CentOS 7. C

Rack-Attack LDAP authentication

Dear, I have a question about GitLab. in the */etc/gitlab/gitlab.rb,* i saw that: gitlab_rails['*rack_attack_git_basic_auth*'] = { 'enabled' => true, # 'ip_whitelist' => ["127.0.0.1"], 'maxretry' => 5, 'findtime'

Rack-attack with LDAP authentication

Dear, I have a question about GitSwarm. in the */etc/gitlab/gitlab.rb,* i saw that: gitlab_rails['*rack_attack_git_basic_auth*'] = { 'enabled' => true, # 'ip_whitelist' => ["127.0.0.1"], 'maxretry' => 5, 'findtime'

LDAP group lookup is failing

We are using the latest release of EE (8.8.2-ee), testing for a move from Github. I am trying to get group sync working but I seem to be having issues with group sync only as LDAP users can login just fine. Both the admin_group setting and the LDAP group sync when trying to tie GitLab groups

Re: LDAP with Multiple Domains

I am not aware of any unique settings for multiple domains on the same domain controller, but I suspect that as long as the configurations are unique, it would work.For reference, our configuration looks like this:  ## LDAP settings  ldap:    enabled: true    servers:      main:        label

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: '

Re: LDAP with Multiple Domains

>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. >> However, the company has seve

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 domai

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

LDAP database in Gitlab

How can we use LDAP database in Gitlab ? Thank you -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this

gitlab EE and LDAP : group search under group_base and other ldap specific questions

Hi, I have a couple of preliminary questions that I can't find an answer in the documentation: - is gitlab able to search for group is sub-nodes of the group_base ? : Saying group_base is ou=branch1,dc=domain,dc=ltd, is it able to look for a group cn=mygroup,ou=project1,ou=branch1,dc=domain,dc=

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&#

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

Hello, I'm trying to configure LDAP access but i can't find a solution to my problem. It's a new 8.5.1 GitLab installations without any registered user. Actually i have an LDAP server where few time email address exist, otherwise it's missing. So there are 2 cases : 1) a

Re: GitLab EE LDAP configuration problem

Try: *uid: 'sAMAccountName'* Wrong configuration "uid 'userPrincipalName' Em quarta-feira, 24 de fevereiro de 2016 12:59:22 UTC-3, Martin Ford escreveu: > > Hi, > > I'm trying to configure a GitLab EE instance (in a docker container) to >

Re: GitLab EE LDAP configuration problem

My issue was so simple it's annoying - I copied some settings from our Jenkins LDAP config, setting the user_filter to be '(userPrincipalName={0})'. Thinking about it this is clearly stupid. Setting user_filter back to '' fixes my issue. -- You received this message b

GitLab EE LDAP configuration problem

Hi, I'm trying to configure a GitLab EE instance (in a docker container) to use LDAP (the AD kind) for authentication and authorisation. The LDAP config section (sanitised) in my /etc/gitlab/gitlab.rb looks like: gitlab_rails['ldap_servers'] = YAML.load <<-'EOS'

Re: allow sign in gitlab if LDAP has email attribute

ing đã viết: > > > Cao Nhan writes: > > > got it. > > Would you mind sharing how you achieved it? > > /M > > > Vào 15:44:38 UTC+7 Thứ Ba, ngày 19 tháng 1 năm 2016, Cao Nhan đã viết: > >> > >> Guys, > >> I am GitLab, Ldap integration

Re: allow sign in gitlab if LDAP has email attribute

Cao Nhan writes: > got it. Would you mind sharing how you achieved it? /M > Vào 15:44:38 UTC+7 Thứ Ba, ngày 19 tháng 1 năm 2016, Cao Nhan đã viết: >> >> Guys, >> I am GitLab, Ldap integration. I want to make gitlab allow only username >> from gitlab, that

Re: allow sign in gitlab if LDAP has email attribute

got it. Vào 15:44:38 UTC+7 Thứ Ba, ngày 19 tháng 1 năm 2016, Cao Nhan đã viết: > > Guys, > I am GitLab, Ldap integration. I want to make gitlab allow only username > from gitlab, that email attribute exist on their account. > How i configure gitlab to do that? > Pleas

allow sign in gitlab if LDAP has email attribute

Guys, I am GitLab, Ldap integration. I want to make gitlab allow only username from gitlab, that email attribute exist on their account. How i configure gitlab to do that? Please help ;) Thanks -- You received this message because you are subscribed to the Google Groups "GitLab"

Re: GitLab ce-8.0.4 FreeIPA LDAP email field problem

Right... We found the issue, although it was quite obscure... FreeIPA uses not one but two LDAP schemas, and depending who is asking, you get to see one or the other. We were binding as: bind_dn: 'cn=ldapbind,cn=groups,cn=accounts,dc=domain,dc=com' This exists, it will work, b

Re: GitLab ce-8.0.4 FreeIPA LDAP email field problem

eeIPA and it seems to work, as > much as users can log in using their ldap password. However we hit a > problem; the LDAP email is not read by GitLab, and a a temp one is assigned. > > Firs thing I tried was to, as admin, update manually the e-mail field for > each user. But at ne

Re: GitLab ce-8.0.4 FreeIPA LDAP email field problem

All, I saw that 8.0.5 has this fix in: v 8.0.5 - Correct lookup-by-email for LDAP logins I installed 8.1.0 The issue still persist, even if I make change to the user profile from the admin account, the e-mail address gets overridden with a temp one on the next login. GitLab, I am using

Re: GitLab ce-8.0.4 FreeIPA LDAP email field problem

> obtained from the account. > > I do not see any indication in the logs about what is going wrong here. > This is preventing us to use gitlab. > > Does anybody know if a lower version will work better? > > Many thanks in advance... > > Guillem > > On Thursday, 8

Re: GitLab ce-8.0.4 FreeIPA LDAP email field problem

import and manege > project , repositories etc. I linked our FreeIPA and it seems to work, as > much as users can log in using their ldap password. However we hit a > problem; the LDAP email is not read by GitLab, and a a temp one is assigned. > > Firs thing I tried was to, as admin, upd

GitLab ce-8.0.4 FreeIPA LDAP email field problem

Hello all, *We have the following issue.* We have gitlab working fine, as admin I can create, import and manege project , repositories etc. I linked our FreeIPA and it seems to work, as much as users can log in using their ldap password. However we hit a problem; the LDAP email is not read by

Ldap (Active Directory) synchronization only working for one user

Hi all, I installed the last Gitlab CE from the packages on a Centos 6. I want to synchronize with my ldap (an Active Directory). This is my config: gitlab_rails['ldap_enabled'] = true gitlab_rails['ldap_servers'] = YAML.load <<-'EOS' # rem

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 wo

LDAP attributes customization

Hello, I'm curious if 4.17.3 supports ldap custom Name mapping to ldap attribtues field inside GitLab. The following pages suggest it should now be working and I upgraded from 7.14.1 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1261 https://gitlab.com/gitlab-org/gitlab-ce

Re: Problem with LDAP

When using method: 'tls', you should point it at the ldap:// port, 389. It will then attempt a LDAP_SERVER_START_TLS_OID "upgrade" to TLS. Or, you can use method: 'ssl', and point it at the ldaps:// port, 636. -- You received this message because you are s

Re: 2FA with LDAP Auth Possible ?

On 30/05/15 15:43, Jason Johnson wrote: Hi, Can anyone confirm if it possible to do LDAP authentication with 2FA auth. When I use my LDAP account the options to enable 2FA disappear from profile >> account. Unfortunately it's not supported in Gitlab CE, but it is in EE for LDA

2FA with LDAP Auth Possible ?

Hi, Can anyone confirm if it possible to do LDAP authentication with 2FA auth. When I use my LDAP account the options to enable 2FA disappear from profile >> account. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe fro

Re: Add LDAP users before they log in

The API fix for skipping confirmation is present in v7.9.0 and following. https://github.com/gitlabhq/gitlabhq/issues/6895 https://github.com/gitlabhq/gitlabhq/commit/5f682094d9b7c985ad62ebe29664bb6fe87b54be -- You received this messag

Re: Add LDAP users before they log in

;: username, > 'password': '1234567890', > "confirm": False, > } > requests.post('https://gitlab.example.com/api/v3/users/', data, headers= > headers) > > > I get the email, dn, name, username from ldap by using python-ldap; I use >

Re: Add LDAP users before they log in

Thanks for sharing! -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.goo

Re: Add LDAP users before they log in

;: email, 'extern_uid': dn, "provider": "ldapmain", "name": name, "username": username, 'password': '1234567890', "confirm": False, } requests.post('https://gitlab.example.com/api/v3/users/'

Re: LDAP search error: Invalid DN Syntax

yntax" 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:check > > Checking LDAP ... > > > > LDAP users with access to your GitLab server (only showing

Re: LDAP search error: Invalid DN Syntax

> > # gitlab-rake gitlab:ldap:check > Checking LDAP ... > > LDAP users with access to your GitLab server (only showing the first 100 > results) > Server: ldapmain > DN: CN=LastName\, FirstName,OU=Users,OU= .. sAMAccountName: > user > > I checked MS TechNet, escapin

LDAP search error: Invalid DN Syntax

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:check Checking LDAP ... LDAP users with acce

Re: gitlab 7.8.2 LDAP issues

LDAP is a pain to setup because there are so many different server configurations... Post the relevant section of your gitlab.rb to make it easier for us to help. When I was setting up LDAP (AD, actually), I used ldapsearch to test different parameter combinations, and then converted these

Re: gitlab 7.8.2 LDAP issues

enerate the actual config files that GitLab read at startup, and "gitlab-ctl hup" to make GitLab re-read the updates config files. HTH, Daniel Serodio On Thursday, March 5, 2015 at 3:26:41 PM UTC-3, Walter Boring wrote: > > I'm trying to debug my LDAP config issues with th

Re: gitlab 7.8.2 LDAP issues

After a long battle, I'm able to get gitlab to connect to my LDAP server. But now, I'm getting invalid credentials everytime I try and auth a new user. I can run RAILS_ENV=production gitlab-rake -v --trace gitlab:ldap:check and I get users listed just fine. The problem I have n

gitlab 7.8.2 LDAP issues

I'm trying to debug my LDAP config issues with the latest gitlab. I know nothing about ruby and all it's confusion of how it works, so I'm probably doing something crazy stupid wrt to rubyness. Anyways, I installed the latest from https://about.gitlab.com/downloads/ on ubuntu 14

Re: How to make LDAP user as admin

gt;>> >>> On Thursday, February 26, 2015 at 2:17:16 PM UTC-8, Maneesh M P wrote: >>>> >>>> Thanks for the reply. Is the bug exists in the issue tracker ? if not I >>>> would like to submit one. >>>> >>>> Thanks, >

Setting full name from LDAP

When using LDAP for user authentication the full name is set same as username, but we need the full name for display in GitLab. Either one of these methods for setting Name for a user from LDAP Name: givenName + sn Name: displayName My LDAP configuration in /etc/gitlab/gitlab.rb gitlab_rails

Re: How to make LDAP user as admin

:16 PM UTC-8, Maneesh M P wrote: >>> >>> Thanks for the reply. Is the bug exists in the issue tracker ? if not I >>> would like to submit one. >>> >>> Thanks, >>> Maneesh >>> >>> On Thursday, February 26, 2015 at 11:02:14 AM

Re: How to make LDAP user as admin

ists in the issue tracker ? if not I >> would like to submit one. >> >> Thanks, >> Maneesh >> >> On Thursday, February 26, 2015 at 11:02:14 AM UTC-8, Daniel Serodio wrote: >>> >>> To make a LDAP user an admin, you should use the Rails console like th

Re: How to make LDAP user as admin

issue tracker ? if not I > would like to submit one. > > Thanks, > Maneesh > > On Thursday, February 26, 2015 at 11:02:14 AM UTC-8, Daniel Serodio wrote: >> >> To make a LDAP user an admin, you should use the Rails console like this: >> >> sudo gitlab-rai

Re: How to make LDAP user as admin

Thanks for the reply. Is the bug exists in the issue tracker ? if not I would like to submit one. Thanks, Maneesh On Thursday, February 26, 2015 at 11:02:14 AM UTC-8, Daniel Serodio wrote: > > To make a LDAP user an admin, you should use the Rails console like this: > > sudo

Re: How to make LDAP user as admin

To make a LDAP user an admin, you should use the Rails console like this: sudo gitlab-rails console u = User.find_by_username("maneesh") u.admin = true u.save exit This may or may not solve your problem, because there's a bug where even being an admin, you can't cr

How to make LDAP user as admin

I have integrated gitlab with our organization LDAP. How can I make a LDAP user as admin ? I have migrated around 200+ repos (which categorized under 16 groups) from gitolite to gitlab. If I have to make a user owner of all the repos, I have to go click each group and add a member. Is there a

Re: gitlab ldap Integration issue : Does it really work????

company was planning to move gitoilite to gitlab enterprise. But first > we wanted to evaluate using community edition. this particular LDAP issue > has been blocking us from evaluating. Thought someone in the community > wouldl be able to help us here:( > We tried the support chat opti

Re: gitlab ldap Integration issue : Does it really work????

Thanks for responding, In a hurry I made lot of mistakes in my mail :( [Tried with both active_directory true and false it didnt work. Our company was planning to move gitoilite to gitlab enterprise. But first we wanted to evaluate using community edition. this particular LDAP issue has been

Re: gitlab ldap Integration issue : Does it really work????

t; >> Op donderdag 12 februari 2015 10:13:58 UTC+1 schreef Maneesh M P: >>> >>> I am still not able to get ldap working with the latest gitlab, here is >>> my configuration. Anything new got introduced in latest version ? can anyone >>> help me to identify t

Re: gitlab ldap Integration issue : Does it really work????

set to true? > > Bram > > Op donderdag 12 februari 2015 10:13:58 UTC+1 schreef Maneesh M P: >> >> I am still not able to get ldap working with the latest gitlab, here is >> my configuration. Anything new got introduced in latest version ? can >> anyone hel

Re: gitlab ldap Integration issue : Does it really work????

Shouldn't "active_directory" set to true? Bram Op donderdag 12 februari 2015 10:13:58 UTC+1 schreef Maneesh M P: > > I am still not able to get ldap working with the latest gitlab, here is my > configuration. Anything new got introduced in latest version ? can anyone &

Re: gitlab ldap Integration issue : Does it really work????

I am still not able to get ldap working with the latest gitlab, here is my configuration. Anything new got introduced in latest version ? can anyone help me to identify the issue ? I get the error * "Could not authorize you from Ldapmain because "Invalid credentials"*

LDAP authentication base configuration

Hi, I'm running GitLab 7.4.2 and trying to set LDAP authentication. I've successfully configured the base property to point on our main users OU, and everything is fine. my next step is to enable all the users in the domain to authenticate so I've tried to set the base to

Re: How disable confirmation email for LDAP accounts?

creveu: >>>> >>>> Hello Michal, >>>> >>>> did you found a solution for this? >>>> >>>> Thank you, >>>> Jonas >>>> >>>> Am Dienstag, 19. November 2013 11:48:15 UTC+1 schrieb Michal Kucera: >>

Re: How disable confirmation email for LDAP accounts?

e e-mail confirmation when loggin in >> with any omniauth authentication method. >> >> Em quinta-feira, 28 de novembro de 2013 08h08min37s UTC-2, Jonas >> Friedmann escreveu: >>> >>> Hello Michal, >>> >>> did you found a solution for this? >&g

Re: "Refresh" email from LDAP

: > > I am using Active Directory for user authentication. Users are able to > authenticate successfully and their email comes correctly. Someone was > recently married and and had their email change. How do I force GitLab to > re-pull the email from Active Directory or 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

LDAP users cannot login after change their DN in LDAP

LDAP users cannot login after change their DN in LDAP. Previously, Gitlab updated LDAP DN in users profile by uid and email fields. Fields uid and email do not change. Gitlab 7.6.2 LDAP settings: enabled: true host: ldap1-some.net base: DC=some,DC=com port: 636 uid: 

Re: what's wrong with my setup? (ldap)

ke the userContainer in your PHP example - You're using sAMAccountName as the uid, but I don't see a sAMAccountName attribute in the return of your find user method. You should probably use "uid" instead. PS.: You forgot to redact your LDAP password :-) HTH, Danie

Re: Adding multipe ldap user_filter

..) (...K2...))(& > (...K3...) (...K4...))). Where KX is the ldap filter condition. > > Regards > > 2015-01-16 3:12 GMT+01:00 Sytse Sijbrandij : >> >> You maybe want to look at >> >> https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/

Re: Adding multipe ldap user_filter

I used the wrong syntax. The syntax for example an or looks like following: | (...K1...) (...K2...)). Mixed with and and (|(& (...K1...) (...K2...))(& (...K3...) (...K4...))). Where KX is the ldap filter condition. Regards 2015-01-16 3:12 GMT+01:00 Sytse Sijbrandij : > You maybe want

Re: Adding multipe ldap user_filter

You maybe want to look at https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/gitlab.yml.md Best regards, Sytse Sijbrandij CEO GitLab B.V. On Thu, Jan 15, 2015 at 7:18 AM, wrote: > I am using the Omnibus GitLab version and would like to add multiple ldap > `user_filt

what's wrong with my setup? (ldap)

5B51404EEAAD3B435B51404EE my config gitlab.rb gitlab_rails['ldap_enabled'] = true gitlab_rails['ldap_servers'] = YAML.load <<-EOS # remember to close this block with 'EOS' below main: # 'main' is the GitLab 'provider ID' of this LDAP

  1   2   3   >