Re: [sipx-dev] Not able to log into the config UI when ldap is running

Thu, 09 Dec 2010 04:18:58 -0800

Hi
      We are able to log into the server when LDAP is down i.e. we need to stop the LDAP server and then log into the config UI.
 
In SIPXCONFIG database, in 'ldap_connection' table  the value for 'principal' field is empty.

Please check the attached file which has the steps to configure LDAP server.

Please look into it and do the needful.

Thanks & Regards,
Chitra.M.S.

Today's Topics:

   1. Re: Not able to log into the config UI when ldap is	running
      (Chitra)


Subject:
Re: [sipx-dev] Not able to log into the config UI when ldap is running
From:
Chitra <[email protected]>
Date:
Wed, 08 Dec 2010 17:57:25 +0530
To:
[email protected]
To:
[email protected]

Hi Laurentiu,

     I will check on these and then I will get back to you as soon as possible.

Thanks,
Chitra

[email protected] wrote: 
Send sipx-dev mailing list submissions to
	[email protected]

To subscribe or unsubscribe via the World Wide Web, visit
	http://list.sipfoundry.org/mailman/listinfo/sipx-dev
or, via email, send a message with subject or body 'help' to
	[email protected]

You can reach the person managing the list at
	[email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of sipx-dev digest..."
  

[please change the subject line when replying]

Today's Topics:

   1. Re: Not able to log into the config UI when ldap is	running
      (Laurentiu Ceausescu)


Subject:
Re: [sipx-dev] Not able to log into the config UI when ldap is running
From:
Laurentiu Ceausescu <[email protected]>
Date:
Wed, 8 Dec 2010 14:20:37 +0200
To:
sipXecs developer discussions <[email protected]>
To:
sipXecs developer discussions <[email protected]>

Hi,

In my opinion LDAP server isn't properly configured.
Are you able to login when the LDAP server is down?
Can you give me more details about how you set up the LDAP server?

in SIPXCONFIG database, in 'ldap_connection' table what is the value for 'principal' field?
Use following commands:
psql SIPXCONFIG -U postgres
SELECT * FROM ldap_connection;

Also please note that sipxconfig.log file in sipxconfig_0.4.4.zip archive is empty.

Thanks,
Laurentiu

On Wed, Dec 1, 2010 at 3:28 PM, Chitra <chitra.ms@thwameva.com> wrote:
Hi Laurentiu,

         We tried setting up the ldap server on the build sipXconfig (4.2.1-018971 2010-08-17T02:19:33 build34)  and we are able to log into the config UI even though the ldap server is running.

But on 0.4.4(sipXconfig (0.4.4-3dc88dd 2010-11-16T00:01:25 build33), we are having the same problem i.e. not able to log into the config UI when ldap is running.

While logging into the config UI(0.4.4), I get this message:
HTTP ERROR: 500

Manager user name  cannot be empty or null.

RequestURI=/sipxconfig/j_acegi_security_check

Powered by Jetty://

Please check the sipxconfig log for both the builds.

Thanks,
Chitra



[email protected] wrote: 
Send sipx-dev mailing list submissions to
	[email protected]

To subscribe or unsubscribe via the World Wide Web, visit
	http://list.sipfoundry.org/mailman/listinfo/sipx-dev
or, via email, send a message with subject or body 'help' to
	[email protected]

You can reach the person managing the list at
	[email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of sipx-dev digest..."
  

[please change the subject line when replying]

Today's Topics:

   1. Re: Importing a file (Tony Graziano)
   2. wd: Not able to log into the config UI when ldap is	running
      (Chitra)
   3. Re: How to build and run? (David Becker)
   4. Re: Interop still around? (Michal Bielicki)
   5. Re: Interop still around? (Andy Spitzer)
   6. Re: Interop still around? (Paul Scheepens)
   7. Re: wd: Not able to log into the config UI when ldap is
      running (Laurentiu Ceausescu)


Subject:
Re: [sipx-dev] Importing a file
From:
Tony Graziano <[email protected]>
Date:
Mon, 29 Nov 2010 01:40:16 -0500
To:
[email protected]
To:
[email protected]		 

The file extension is not important. Your import file contained data that
could be imported in the correct format. I don't think a jira is in order
(but maybe a typing class is, ;>)  ).

If you would like an example of the priper format, perform an export.
============================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

----- Original Message -----
From: [email protected]
<[email protected]>
To: [email protected] <[email protected]>
Sent: Mon Nov 29 01:11:32 2010
Subject: [sipx-dev] Importing a file

Hi All,
             In system->Import/Export.For import option,whether we can
import a  .txt file.Because I created a Text file with some text in
it.Then I Import the Txt file   through Config UI.It say File has been
successfully uploaded. Go to Job Status page to monitor import operation
progress.In job status Import data was completed and in User's Page the
user is created.I had attached a file and screen shot please check it
            Could you please advice me whether this is an expected
behavior OR a Bug needs to be raised.
Regards
Venkateshwaran T


Subject:
[sipx-dev] wd: Not able to log into the config UI when ldap is running
From:
Chitra <[email protected]>
Date:
Mon, 29 Nov 2010 14:51:03 +0530
To:
[email protected]
To:
[email protected]

Hi

    I had sent a mail to Laurentiu regarding this issue. But I haven't received any message as yet. Hence I am sending the sipxconfig log file and the error message what we get when we log into the Config UI when ldap server is running.

Please check the sipxconfig log message:

"2010-11-24T05:16:55.029000Z":1368:JAVA:WARNING:sipx-test.ttplservices.com:P1-17:00000000:LdapContextSource:"Property 'userName' not set - anonymous context will be used for read-write operations"
"2010-11-24T05:16:55.046000Z":1369:JAVA:WARNING:sipx-test.ttplservices.com:P1-17:00000000:LdapContextSource:"Property 'userName' not set - anonymous context will be used for read-write operations"
"2010-11-24T05:16:55.061000Z":1370:JAVA:WARNING:sipx-test.ttplservices.com:P1-17:00000000:sipXconfig-web:"/sipxconfig/j_acegi_security_check: "
java.lang.IllegalArgumentException: Manager user name  cannot be empty or null.
   at org.springframework.util.Assert.hasLength(Assert.java:136)
   at org.acegisecurity.ldap.DefaultInitialDirContextFactory.setManagerDn(DefaultInitialDirContextFactory.java:293)
   at org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.getDirFactory(ConfigurableLdapAuthenticationProvider.java:135)
   at org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.createProvider(ConfigurableLdapAuthenticationProvider.java:120)
   at org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.initialize(ConfigurableLdapAuthenticationProvider.java:108)
   at org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.supports(ConfigurableLdapAuthenticationProvider.java:97)
   at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:194)
   at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
   at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
   at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
   at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
   at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
   at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
   at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149)
   at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
   at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
   at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
   at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
   at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
   at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:635)
   at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
   at org.mortbay.http.HttpServer.service(HttpServer.java:954)
   at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
   at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
   at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
   at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
   at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
   at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
"2010-11-24T05:17:43.218000Z":1371:JAVA:WARNING:sipx-test.ttplservices.com:P1-8:00000000:LdapContextSource:"Property 'userName' not set - anonymous context will be used for read-write operations"
"2010-11-24T05:17:43.229000Z":1372:JAVA:WARNING:sipx-test.ttplservices.com:P1-8:00000000:LdapContextSource:"Property 'userName' not set - anonymous context will be used for read-write operations"
"2010-11-24T05:17:43.258000Z":1373:JAVA:WARNING:sipx-test.ttplservices.com:P1-8:00000000:sipXconfig-web:"/sipxconfig/j_acegi_security_check: "
java.lang.IllegalArgumentException: Manager user name  cannot be empty or null.
   at org.springframework.util.Assert.hasLength(Assert.java:136)
   at org.acegisecurity.ldap.DefaultInitialDirContextFactory.setManagerDn(DefaultInitialDirContextFactory.java:293)
   at org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.getDirFactory(ConfigurableLdapAuthenticationProvider.java:135)
   at org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.createProvider(ConfigurableLdapAuthenticationProvider.java:120)
   at org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.initialize(ConfigurableLdapAuthenticationProvider.java:108)
   at org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.supports(ConfigurableLdapAuthenticationProvider.java:97)
   at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:194)
   at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
   at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
   at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
   at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
   at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
   at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
   at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149)
   at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
   at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
   at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
   at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
   at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
   at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:635)
   at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
   at org.mortbay.http.HttpServer.service(HttpServer.java:954)
   at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
   at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
   at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
   at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
   at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
   at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

And the error message what we get when logging into the UI as superadmin:

HTTP ERROR : 500
Manager user name cannot be empty or null.

RequestURI=/sipxconfig/j_acegi_security_check

Powered by Jetty://




Subject:
Re: [sipx-dev] How to build and run?
From:
David Becker <[email protected]>
Date:
Mon, 29 Nov 2010 10:38:32 +0100
To:
[email protected]
To:
[email protected]

Am 26.11.2010 17:06, schrieb Douglas Hubler:
On Fri, Nov 26, 2010 at 6:45 AM, David Becker
<[email protected]>  wrote:
Am 26.11.2010 09:41, schrieb David Becker:
Am 24.11.2010 13:24, schrieb David Becker:
Am 24.11.2010 13:23, schrieb Douglas Hubler:
On Wed, Nov 24, 2010 at 7:09 AM, David Becker
<[email protected]>      wrote:
Am 24.11.2010 13:02, schrieb Douglas Hubler:
Having source and rpm install on a system is not supported. Any reason
u need this


I followed the instructions in
http://sipx-wiki.calivia.com/index.php/Setting_up_a_development_environment
for CentOS and the yum install commands installed sipx.
where does it say install sipxecs?  you do install sipx-openfire
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
I guess it's a dependency of some package or something but whenever I
run that command it installs sipx fully.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
Okay, sipx-jasperreports-deps is listed in the Wiki, that's obsoleted by
sipxconfig so yum downloads the entirety of SipX. I'll try running
without that.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
It compiles but still won't run, the ssl-keystore and some httpd configs
are missing (note that I am running this as root):

httpd: Syntax error on line 1087 of
/usr/local/sipx/etc/sipxpbx/httpd.conf: Could not open configuration
file /usr/local/sipx/etc/sipxpbx/httpd-sipxchange-common.conf: No such
file or directory
/usr/local/sipx/libexec/sipXecs/setup.d/011_sipx-config-httpd-access:
line 20: /usr/local/sipx/etc/sipxpbx/httpd-sipxchange-common.conf: Keine
Berechtigung (Permission Denied)
/usr/local/sipx/libexec/sipXecs/setup.d/012_sipx-config-vxml-domain:
line 22: /usr/local/sipx/share/www/doc/vm_vxml/root.vxml: Keine
Berechtigung (Permission Denied)
Exception in thread "main" java.io.FileNotFoundException:
/usr/local/sipx/etc/sipxpbx/ssl/ssl-web.keystore (Permission denied)
         at java.io.FileOutputStream.open(Native Method)
         at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
         at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
         at
org.sipfoundry.commons.sipkeystorebuilder.sipkeystorebuilder.main(Unknown Source)
sipXpbx:
sipXpbx: sipXpbx configuration problems found:
sipXpbx:
sipXpbx: Check Apache configuration
sipXpbx:   httpd: Syntax error on line 1087 of
/usr/local/sipx/etc/sipxpbx/httpd.conf: Could not open configuration
file /usr/local/sipx/etc/sipxpbx/httpd-sipxchange-common.conf: No such
file or directory
sipXpbx:

2 things
1.) Did you specify SIPXPBXUSER=`whoami`  in your call to ./configure?
2.) Did you run after install:?
   sudo /usr/local/sipx/etc/init.d/sipxecs-setup

If you did not, you really need to delete all of /usr/local/sipx/* and
start over on build.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
Yes and yes.



Subject:
Re: [sipx-dev] Interop still around?
From:
Michal Bielicki <[email protected]>
Date:
Mon, 29 Nov 2010 12:51:24 +0100
To:
sipXecs developer discussions <[email protected]>
To:
sipXecs developer discussions <[email protected]>		 

That site is unreachable

Am 23.11.2010 um 16:13 schrieb Douglas Hubler:

  
On Mon, Nov 22, 2010 at 1:43 PM, Michal Bielicki
<[email protected]> wrote:
    
Whats required for that ?
      
I wouldn't know, I assumed Andy would know having used the service before.

Paul, good to know this service is running, should to the trick at
least for a little while.
 http://interop.sipsw.com/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
    
Michal Bielicki
Geschäftsführer / CEO

Seventh Signal Ltd. & Co. KG
Weigandufer 45, Büro 115, D-12059 Berlin
Voice: +49 30 60988730

Amtsgericht Charlottenburg HRA 44413 B
Ust.-ID: DE266981999
Geschäftsführer: Michal Bielicki
Persönlich Haftende Gesellschafterin:
Seventh Signal Ltd, 69 Great Hampton St. Birmingham, 
B18 6EW, GB, Company Nr.: 06889439
WWW.: http://www.seventhsignal.de


Subject:
Re: [sipx-dev] Interop still around?
From:
"Andy Spitzer" <[email protected]>
Date:
Mon, 29 Nov 2010 08:53:36 -0500
To:
"sipXecs developer discussions" <[email protected]>
To:
"sipXecs developer discussions" <[email protected]>

Woof!

On Mon, 29 Nov 2010 06:51:24 -0500, Michal Bielicki <[email protected]> wrote:

That site is unreachable

That site being interop.sipsw.com is unreachable for me as well.

Interestingly, it seems that
  http://interop.sipxecs.org/

is still around, but I cannot get registrations to be accepted.  No SIP responses at all.

--Woof!



Subject:
Re: [sipx-dev] Interop still around?
From:
Paul Scheepens <[email protected]>
Date:
Mon, 29 Nov 2010 15:09:09 +0100
To:
sipXecs developer discussions <[email protected]>
To:
sipXecs developer discussions <[email protected]>

I think somebody that's on this user-list is responsible for the fact that the site is down now......
It was up when I sent the e-mail out last week.

> Woof!
>
> On Mon, 29 Nov 2010 06:51:24 -0500, Michal Bielicki  
> <[email protected]> wrote:
>
> > That site is unreachable
>
> That site being interop.sipsw.com is unreachable for me as well.
>
> Interestingly, it seems that
>    http://interop.sipxecs.org/
>
> is still around, but I cannot get registrations to be accepted.  No SIP  
> responses at all.
>
> --Woof!
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Subject:
Re: [sipx-dev] wd: Not able to log into the config UI when ldap is running
From:
Laurentiu Ceausescu <[email protected]>
Date:
Mon, 29 Nov 2010 18:17:26 +0200
To:
sipXecs developer discussions <[email protected]>
To:
sipXecs developer discussions <[email protected]>



On Mon, Nov 29, 2010 at 11:21 AM, Chitra <chitra.ms@thwameva.com> wrote:
Hi

    I had sent a mail to Laurentiu regarding this issue. But I haven't
received any message as yet.

Sorry, but I didn't get any mail from you.
Please reply to the whole list on matters like this in order to give a chance to react to all devs.
 
Hence I am sending the sipxconfig log file
and the error message what we get when we log into the Config UI when
ldap server is running.

Please check the sipxconfig log message:

Looking on the log looks like the problem is in the ConfigurableLdapAuthenticationProvider class, line 135:
...
dirContextFactory.setManagerDn(params.getPrincipal());
...

The error 'manager user name  cannot be empty or null' tell me that the user name somehow is missing.
But I don't understand how it could be properly configured LDAP server without the user name.
So, my questions are:
 - assuming that the LDAP server is up and running, are you able to import users from LDAP (LDAP page/Import tab)?
 - what is the value of 'Authentification Option' combobox under LDAP page/Settings tab?
Also can you specific more details abut the scenario that you test?

Thanks,
Laurentiu
 

"2010-11-24T05:16:55.029000Z":1368:JAVA:WARNING:sipx-test.ttplservices.com:P1-17:00000000:LdapContextSource:"Property
'userName' not set - anonymous context will be used for read-write
operations"
"2010-11-24T05:16:55.046000Z":1369:JAVA:WARNING:sipx-test.ttplservices.com:P1-17:00000000:LdapContextSource:"Property
'userName' not set - anonymous context will be used for read-write
operations"
"2010-11-24T05:16:55.061000Z":1370:JAVA:WARNING:sipx-test.ttplservices.com:P1-17:00000000:sipXconfig-web:"/sipxconfig/j_acegi_security_check:
"
java.lang.IllegalArgumentException: Manager user name  cannot be empty
or null.
   at org.springframework.util.Assert.hasLength(Assert.java:136)
   at
org.acegisecurity.ldap.DefaultInitialDirContextFactory.setManagerDn(DefaultInitialDirContextFactory.java:293)
   at
org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.getDirFactory(ConfigurableLdapAuthenticationProvider.java:135)
   at
org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.createProvider(ConfigurableLdapAuthenticationProvider.java:120)
   at
org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.initialize(ConfigurableLdapAuthenticationProvider.java:108)
   at
org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.supports(ConfigurableLdapAuthenticationProvider.java:97)
   at
org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:194)
   at
org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
   at
org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
   at
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
   at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
   at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
   at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
   at
org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149)
   at
org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
   at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
   at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
   at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
   at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
   at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:635)
   at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
   at org.mortbay.http.HttpServer.service(HttpServer.java:954)
   at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
   at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
   at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
   at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
   at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
   at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
"2010-11-24T05:17:43.218000Z":1371:JAVA:WARNING:sipx-test.ttplservices.com:P1-8:00000000:LdapContextSource:"Property
'userName' not set - anonymous context will be used for read-write
operations"
"2010-11-24T05:17:43.229000Z":1372:JAVA:WARNING:sipx-test.ttplservices.com:P1-8:00000000:LdapContextSource:"Property
'userName' not set - anonymous context will be used for read-write
operations"
"2010-11-24T05:17:43.258000Z":1373:JAVA:WARNING:sipx-test.ttplservices.com:P1-8:00000000:sipXconfig-web:"/sipxconfig/j_acegi_security_check:
"
java.lang.IllegalArgumentException: Manager user name  cannot be empty
or null.
   at org.springframework.util.Assert.hasLength(Assert.java:136)
   at
org.acegisecurity.ldap.DefaultInitialDirContextFactory.setManagerDn(DefaultInitialDirContextFactory.java:293)
   at
org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.getDirFactory(ConfigurableLdapAuthenticationProvider.java:135)
   at
org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.createProvider(ConfigurableLdapAuthenticationProvider.java:120)
   at
org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.initialize(ConfigurableLdapAuthenticationProvider.java:108)
   at
org.sipfoundry.sipxconfig.security.ConfigurableLdapAuthenticationProvider.supports(ConfigurableLdapAuthenticationProvider.java:97)
   at
org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:194)
   at
org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
   at
org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
   at
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
   at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
   at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
   at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
   at
org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149)
   at
org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
   at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
   at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
   at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
   at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
   at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:635)
   at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
   at org.mortbay.http.HttpServer.service(HttpServer.java:954)
   at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
   at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
   at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
   at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
   at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
   at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

And the error message what we get when logging into the UI as superadmin:

HTTP ERROR : 500
Manager user name cannot be empty or null.

RequestURI=/sipxconfig/j_acegi_security_check

Powered by Jetty://

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/


_______________________________________________
sipx-dev mailing list
[email protected]
http://list.sipfoundry.org/mailman/listinfo/sipx-dev

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/


_______________________________________________
sipx-dev mailing list
[email protected]
http://list.sipfoundry.org/mailman/listinfo/sipx-dev
  

_______________________________________________
sipx-dev mailing list
[email protected]
http://list.sipfoundry.org/mailman/listinfo/sipx-dev
  
LDAP SERVER SETTINGS:


After installing the SIPXCHANGE :

Login as root user

1.From the console run the command to install the LDAP Server

yum install openldap openldap-devel nss_ldap openldap-clients openldap-servers


2.Get the encrypted LDAP password by:

  slappasswd

This will prompt for a password.

Remove the # Command(line should not be commented) Enter the password (need not 
be the root password eg:1234) which will generate the encrypted password like

"{SSHA}5WcnZ/3lXJXf72pyS5Nv2z3sjNVrpm2m".

SAVE THIS PASSWORD> THIS IS REQUIRED.


3.Navigate to

/etc/openldap and modify follwing parameters in "slapd.conf" file:

database        bdb
suffix          "dc=ttplservices,dc=com"
rootdn          "cn=Manager,dc=ttplservices,dc=com"
rootpw          PASTE THE ENCRYPTED PASSWORD HERE


4.Modify following parameter in "ldap.conf" file in

/etc/openldap/

Remove the # Command
BASE    dc=ttplservices, dc=com
URI     ldap://176.25.2.247:389

5. Start the LDAP Server by running command

etc/init.d/ldap restart

6.Check the LDAP status by

/etc/init.d/ldap status


7. Add the users to th LDAP Server.

Navigate to /etc/openldap give the command

vi inital_import.ldif

Copy the contents of inital_import.ldif file provided into this.

REFER TO inital_import.ldif file provided. Then run the command

ldapadd -x -W -D "cn=Manager,dc=ttplservices,dc=com" -f ./initial_import.ldif

Then it asks for ldap password.


8. Verify the LDAP database, for added user using

ldapsearch -x


9. To Modify the Existing user:

Modify the user details like uid/givenname/sn/telephonenumber in the 
initial_import.ldif file, then run the command

ldapmodify -x -W -D "cn=Manager,dc=ttplservices,dc=com" -f ./initial_import.ldif

10. Verify the LDAP database, for modified user using

ldapsearch -x

11. To Delete the LDAP user

ldapdelete -x -W -D "cn=Manager,dc=ttplservices,dc=com" "{attribute}"

example of attribute is "cn=Hiranmayee Sahoo,ou=Junior Emplyes,o=TTPL 
QA,dc=ttplservices,dc=com"
dn is the attribute.

12.Verify the LDAP database, for deleted user using

ldapsearch -x


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to