[ 
https://issues.apache.org/jira/browse/MRM-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emilie closed MRM-1943.
-----------------------
       Resolution: Not A Bug
    Fix Version/s: 2.2.3

This wasn't a bug - I had to manually edit the properties file:


ldap.config.groups.class group
ldap.config.groups.member Member
ldap.config.mapper.attribute.user.id  sAMAccountName
ldap.config.user.attribute sAMAccountName

Remove user cache 

> LDAP Verification working - no Groups show up
> ---------------------------------------------
>
>                 Key: MRM-1943
>                 URL: https://issues.apache.org/jira/browse/MRM-1943
>             Project: Archiva
>          Issue Type: Bug
>          Components: redback
>    Affects Versions: 2.2.3
>         Environment: Archiva 2.2.1 - Windows Server 2012 Datacenter - Java 8 
> Update 131
>            Reporter: Emilie
>             Fix For: 2.2.3
>
>         Attachments: archiva.xml, LDAP_Config.png, LDAP_GroupRole.png
>
>
> I am trying to setup Archiva (first time) In my test environment to do a 
> proof of concept. 
> This is the first time working with Archiva - so likely I am missing 
> something.
> LDAP is running on the same VM as Archiva - LDAP verification works, but no 
> groups are displayed. 
> In the Archiva log file I'm seeing this when I try to add a group mapping: 
> 2017-05-24 09:13:02,127 [qtp2084363060-25] ERROR 
> org.apache.archiva.redback.rest.services.DefaultLdapGroupMappingService [] - 
> Unprocessed Continuation Reference(s)
> org.apache.archiva.redback.common.ldap.MappingException: Unprocessed 
> Continuation Reference(s)
>       at 
> org.apache.archiva.redback.common.ldap.role.DefaultLdapRoleMapper.getAllGroups(DefaultLdapRoleMapper.java:183)
>  ~[redback-common-ldap-2.4.jar:2.4]
>       at 
> org.apache.archiva.redback.rest.services.DefaultLdapGroupMappingService.getLdapGroups(DefaultLdapGroupMappingService.java:79)
>  [redback-rest-services-2.4.jar:2.4]
> I have attached my configuration for your review



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to