[gitorious] Re: All LDAP functionality fails after update containing ldap group feature

2013-04-12 Thread Chiku Linu
Hi

I got same problem too.
It's empty even in teams there are few ldap group teams.
v2.4.12

Le vendredi 18 janvier 2013 23:23:45 UTC+1, Paul Ruiz a écrit :

 Since updating to the tag that included ldap groups; 
   new users aren't able to login/auto-register while previously existing 
 users are able to continue logging in,
   viewing /teams displays no teams though teams exist in the DB and 
 results in an exception (attached:exception2.txt)
   viewing projects created before the update results results in a Sorry, 
 something went wrong page and a logged exception (attached:exception1.txt)
   new projects can be created but 'Edit project'-'Transfer ownership to a 
 group' is empty.

 LDAP worked before the update and authorization.yml config change. 
  Removing the group related LDAP options and restarting has no effect.  A 
 packet capture shows that gitorious never attempts to contact the 
 configured LDAP host.  I've attached the exceptions and my gitorious.yml 
 and authentication.yml.

 Gitorious v2.4.5
 Centos 6.3 x86_64 with all updates.
 Gitorious originally installed using Community Edition installer, 
 11/25/2012, and manually updated with each point release.

 Any help would be much appreciated.  If I can't figure this out soon, I'll 
 need to start over from scratch.


-- 
-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[gitorious] Re: All LDAP functionality fails after update containing ldap group feature

2013-01-18 Thread Paul Ruiz
For some reason Google Groups won't let me attach and post files (An error 
(#340) occurred while communicating with the server)  so they're inline

gitorious.yml:
production: 
  cookie_secret: 
  repository_base_path: /var/www/gitorious/repositories
  extra_html_head_data:
  system_message:  
  gitorious_client_port: 80
  gitorious_client_host: localhost
  gitorious_host: gitorious.tsi.lan
  gitorious_user: git
  gitorious_support_email: pr...@foo.com
  exception_notification_emails: pr...@foo.com 
  mangle_email_addresses: false
  public_mode: true
  locale: en
  disable_record_throttling: true
  enable_repository_dir_sharding: false
  enable_private_repositories: true
  repos_and_projects_private_by_default: false
  archive_cache_dir: /var/www/gitorious/tarballs-cache
  archive_work_dir: /var/www/gitorious/tarballs-work  
  only_site_admins_can_create_projects: false
  hide_http_clone_urls: false
  use_ssl: true
  is_gitorious_dot_org: false
  default_license: None
  ssh_fingerprint: ae:5a:33:c5:fb:7d:e9:a9:30:91:3e:85:cf:6d:29:f7
  turn_on_public_diagnostic_summary_page: true
  site_name: Corp Gitorious
  logo_url: /logo.gif
  custom_username_label: TSI.lan Username
  use_ldap_authorization: true
  sender_email_address: Gitorious no-re...@foo.com


authentication.yml:
production:
  disable_default: false
  methods:
- adapter: Gitorious::Authentication::LDAPAuthentication
  host: '10.16.161.31'
  port: 389
  base_dn: 'DC=tsi,DC=lan'
  bind_username: 'bindu...@tsi.lan'
  bind_password: 'foo'
  #group_search_dn: 'OU=TSI Groups,OU=User Groups,DC=tsi,DC=lan'
  #membership_attribute_name: memberof
  #members_attribute_name: member
  # Group lookup cache time, default is 0 (no caching)
  cache_expiry: 60
  user_filter:
  username_attribute: 'sAMAccountName'
  encryption: 'none'
  login_attribute: 'uid'
  distinguished_name_template: '{}@tsi.lan'
  attribute_mapping:
mail: 'email'

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com