Open Source Document Management System | OpenKM

PostPosted:**Mon Mar 11, 2013 12:40 pm**

I have OKM 6.2 CE configure with ActiveDomain login.
This is functioning correctly both for administrator and normal users.

However the login time from entering username/password to being fully logged in is extremely long - circa 2 minutes!

Is this normal for an AD setup?

OpenKM and AD are on separate machines but same "office" and LAN.

PostPosted:**Tue Mar 12, 2013 11:57 am**

How much users do you got in ldap ?

I suggest you filter only for users who real will have access to OpenKM, take a look here http://wiki.openkm.com/index.php/Ldap-example3 how filter users who are members of ROLE_ADMIN or ROLE_USER

PostPosted:**Tue Mar 12, 2013 2:36 pm**

Only 30 users, I will have a look at the wiki example, thanks

PostPosted:**Wed Mar 13, 2013 6:40 pm**

30 Users should be a fast login, you got other kind of problem. Test networking speed and ensure from your server you resolv correctly all ldap principal nodes.

I suggest you browser ldap with http://technet.microsoft.com/en-us/sysi ... 63907.aspx utility:
Normally you'll see main nodes like dc=company,dc=local among others, I suggest you add in hosts files entries like
ip_server company.local etc... ( the main three nodes will give you some idea which hosts names should be added )

PostPosted:**Thu Mar 21, 2013 11:43 pm**

ok so I have tried a number of things

1) The active directory server (10.10.1.2) is named in the hosts file of OpenKM (10.10.1.10) - no change to login times
2) Have configured according to ldap example 3 - http://wiki.openkm.com/index.php/Ldap-example3 - no change to login times

What I am seeing is initial login of any user after period of no use is 2 minutes.
If logout and login as another user, login is immediate < 5sec.

Running OpenKM on a 64bit Ubuntu server VM which is hosted on a VMware ESXi server.
For the initial testing, it is allocated 2 CPU and 2GB ram which should be sufficient.

Anything else I can try?

PostPosted:**Sat Mar 23, 2013 9:12 pm**

if you connect with ldap explorer utility http://technet.microsoft.com/en-us/sysi ... 63907.aspx

You'll see several nodes like dc=some,dc=company,com etc... normally 3-4 principal nodes with different names, I suggest you add some ip resolution in your host file like:

Code: Select all

10.10.10.2 some.company.com 
10.10.10.2 schema.some.company.com 
10.10.10.2 configuration.some.company.com 
etc...

PostPosted:**Mon Mar 25, 2013 9:58 am**

Thanks tried that but it has had no visible effect on login times.
The initial login is still circa 2 minutes for AD authentication which makes it unusable unless this can be solved.

Is there any logs I can provide which might point out what the problem is?

PostPosted:**Tue Mar 26, 2013 10:11 pm**

Edit /conf/log4j.properties and at ends add something like :

Code: Select all

log4j.logger.org.springframework.security.ldap=DEBUG

Note that I have never got a installation with this excessibe delay time, you got something strange.

PostPosted:**Fri Mar 29, 2013 10:51 am**

As I described before, I have followed http://wiki.openkm.com/index.php/Ldap-example3 and any further info provided.

ok here is my OpenKM.xml file

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<beans:beans xmlns:beans="http://www.springframework.org/schema/beans"
             xmlns:security="http://www.springframework.org/schema/security"
             xmlns:task="http://www.springframework.org/schema/task"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://www.springframework.org/schema/beans
                                 http://www.springframework.org/schema/beans/spring-beans-3.1.xsd
                                 http://www.springframework.org/schema/security
                                 http://www.springframework.org/schema/security/spring-security-3.1.xsd
                                 http://www.springframework.org/schema/task
                                 http://www.springframework.org/schema/task/spring-task-3.1.xsd">

<security:authentication-manager alias="authenticationManager">
     <security:authentication-provider ref="ldapAuthProvider" />
  </security:authentication-manager>

<beans:bean id="contextSource" class="org.springframework.security.ldap.DefaultSpringSecurityContextSource">
  <beans:constructor-arg value="ldap://10.10.1.2"/>
 <beans:property name="userDn" value="CN=administrator,CN=Users,DC=fw,DC=local"/>
  <beans:property name="password" value="pass"/>

  <beans:property name="baseEnvironmentProperties">
     <beans:map>
        <beans:entry>
          <beans:key>
            <beans:value>java.naming.referral</beans:value>
          </beans:key>
          <beans:value>follow</beans:value>
        </beans:entry>
      </beans:map>
   </beans:property>
</beans:bean>

<beans:bean id="ldapAuthProvider" class="org.springframework.security.ldap.authentication.LdapAuthenticationProvider">
  <beans:constructor-arg>
    <beans:bean class="org.springframework.security.ldap.authentication.BindAuthenticator">
      <beans:constructor-arg ref="contextSource"/>
      <beans:property name="userSearch" ref="userSearch"/>
    </beans:bean>
  </beans:constructor-arg>
  <beans:constructor-arg>
    <beans:bean class="org.springframework.security.ldap.userdetails.DefaultLdapAuthoritiesPopulator">
      <beans:constructor-arg ref="contextSource"/>
      <beans:constructor-arg value="DC=fw,DC=local"/>
      <beans:property name="groupSearchFilter" value="member={0}"/>
      <beans:property name="groupRoleAttribute" value="cn"/>
      <beans:property name="searchSubtree" value="true" />
      <beans:property name="convertToUpperCase" value="false" />
      <beans:property name="rolePrefix" value="" />
    </beans:bean>
  </beans:constructor-arg>
</beans:bean>

<beans:bean id="userSearch" class="org.springframework.security.ldap.search.FilterBasedLdapUserSearch">
  <beans:constructor-arg index="0" value="DC=fw,DC=local" />
  <beans:constructor-arg index="1" value="(&(sAMAccountName={0})(|(memberOf=CN=ROLE_ADMIN,OU=OpenKM,DC=fw,DC=local)(memberOf=CN=ROLE_USER,OU=OpenKM,DC=fw,DC=local)))" />
  <beans:constructor-arg index="2" ref="contextSource" />
  <beans:property name="searchSubtree" value="true" />
</beans:bean>

</beans:beans>

My hosts file contains:

Code: Select all

127.0.0.1 localhost
10.10.1.10 library.fw.local library
10.10.1.2 SBSSERVER.fw.local SBSSERVER
10.10.1.2 schema.SBSSERVER.fw.local
10.10.1.2 configuration.SBSSERVER.fw.local
10.10.1.2 DomainDnsZones.SBSSERVER.fw.local
10.10.1.2 ForestDnsZones.SBSSERVER.fw.local


# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

My Catalina.log file is attached in dropbox as couldn't upload here
https://www.dropbox.com/s/ep5xo1a5u9f09n3/catalina.zip

Screenshot from the AD tool recommended
https://www.dropbox.com/s/jozosepc7mgyptm/Capture.jpg

I don't think I have anything odd but at this stage I'm at a loss as to how to solve this.

PostPosted:**Fri Mar 29, 2013 8:10 pm**

Do you have a reverse dns zone with your AD and openkm server entries? We had similar problem on linux clients, there's a bug in ubuntu 12.04 which makes it always perform a reverse lookup on the host name, and the services that depend on it wait 15s for a reply every time.

PostPosted:**Sun Mar 31, 2013 5:38 pm**

I suggest add in /etc/hosts the ip for fw.local
10.10.1.2 fw.local

and all the other subdomains associated with it. Put here your /etc/hosts file to ensure is right.

PostPosted:**Sun Mar 31, 2013 6:58 pm**

here is the contents of my etc/hosts file.

Code: Select all

administrator@library:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.0.1 library
127.0.0.1 library.fw.local
10.10.1.10 library library.fw.local
10.10.1.2 fw.local
10.10.1.2 SBSSERVER SBSSERVER.fw.local
10.10.1.2 schema.SBSSERVER.fw.local
10.10.1.2 configuration.SBSSERVER.fw.local
10.10.1.2 DomainDnsZones.SBSSERVER.fw.local
10.10.1.2 ForestDnsZones.SBSSERVER.fw.local

@ dejanfc - no reverse dns zones. Thought ipv6 could be causing it so tried disabling it too.

No changes to login times yet.

PostPosted:**Mon Apr 01, 2013 9:29 am**

In the image you have black edited some name, we will call as fw but obviously is not fw, right ?

Code: Select all

10.10.1.2 fw.local
10.10.1.2 SBSSERVER SBSSERVER.fw.local
10.10.1.2 schema.fw.local
10.10.1.2 Schema.Configuration.fw.local
10.10.1.2 Configuration.fw.local
10.10.1.2 DomainDnsZones.fw.local
10.10.1.2 ForestDnsZones.fw.local

See I have changed schema.fw.local to Schema.configuration.fw.local and other in same way.

PostPosted:**Tue Apr 02, 2013 1:31 pm**

yes, not fw but similar.

Your suggested changes to the /etc/hosts has worked - Thank you very much for all the help, really appreciated.
Instant login now!

PostPosted:**Thu Apr 04, 2013 4:49 pm**

I will add a note in wiki that can be useful for other users. I have added here: http://wiki.openkm.com/index.php/Troubl ... _with_ldap

Open Source Document Management System | OpenKM

OKM 6.2 login time?

OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?

Re: OKM 6.2 login time?