This discussion is archived
2 Replies Latest reply: Mar 17, 2011 1:27 AM by 415983 RSS

Oracle OnTrack Ldap Realm Problem.

829207 Newbie
Currently Being Moderated
Hi,

After configuring my ldap realm (this is an OpenLdap server), I am getting this error from the Weblogic logfile.


####<Mar 16, 2011 3:15:23 PM ART> <Info> <waggle.server.servlet.XMethod> <togo> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <cbc1c7646c36152c:3c8587d9:12ebf7c1653:-8000-0000000000000989> <1300299323213> <BEA-000000> <Exception during method setup and execute (/Login).
waggle.server.login.exceptions.XLoginException: The Application is closed at the current time.
     at waggle.server.login.XLoginManager.setLoginData(XLoginManager.java:138)
     at waggle.server.login.handlers.XLoginHandlerParameters.login(XLoginHandlerParameters.java:57)
     at waggle.server.login.XLoginManager.login(XLoginManager.java:94)
     at waggle.server.servlet.XMethod.execute(XMethod.java:469)
     at waggle.server.servlet.XServletRequest.service(XServletRequest.java:119)
     at waggle.server.servlet.XServlet.service(XServlet.java:132)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at waggle.server.filter.header.XSimpleCacheHeadersFilter.doFilter(XSimpleCacheHeadersFilter.java:72)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at waggle.server.filter.gzip.XGZipFilter.doFilter(XGZipFilter.java:169)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)

In the OpenLdap logfile, I got

Mar 16 14:38:09 osaka slapd[1390]: conn=3808 fd=26 ACCEPT from IP=***.***.***.***:64711 (IP=0.0.0.0:636)
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 fd=26 TLS established tls_ssf=128 ssf=128
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=0 BIND dn="****************" method=128
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=0 BIND dn="****************" mech=SIMPLE ssf=0
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=0 RESULT tag=97 err=0 text=
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=1 SRCH base="dc=osaka" scope=2 deref=0 filter="(&(objectClass=inetOrgPerson)(mail=andres.de.barbara@grupomost.com))"
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=1 SRCH attr=dn
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text=
Mar 16 14:38:09 osaka slapd[1390]: conn=3809 fd=28 ACCEPT from IP=***.***.***.***:64712 (IP=0.0.0.0:636)
Mar 16 14:38:09 osaka slapd[1390]: conn=3809 fd=28 TLS established tls_ssf=128 ssf=128
Mar 16 14:38:09 osaka slapd[1390]: conn=3809 op=0 BIND dn="uid=********,ou=Users,dc=osaka" method=128
Mar 16 14:38:09 osaka slapd[1390]: conn=3809 op=0 BIND dn="uid=********,ou=Users,dc=osaka" mech=SIMPLE ssf=0
Mar 16 14:38:09 osaka slapd[1390]: conn=3809 op=0 RESULT tag=97 err=0 text=
Mar 16 14:38:09 osaka slapd[1390]: conn=3809 op=1 UNBIND
Mar 16 14:38:09 osaka slapd[1390]: conn=3809 fd=28 closed
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=2 EXT oid=0.0.0.0
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=2 do_extended: unsupported operation "0.0.0.0"
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=2 RESULT tag=120 err=2 text=unsupported extended operation
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=3 SRCH base="dc=osaka" scope=2 deref=0 filter="(&(objectClass=inetOrgPerson)(mail=andres.de.barbara@grupomost.com))"
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=3 SRCH attr=dn
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=3 SEARCH RESULT tag=101 err=0 nentries=1 text=
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=4 EXT oid=0.0.0.0
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=4 do_extended: unsupported operation "0.0.0.0"
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=4 RESULT tag=120 err=2 text=unsupported extended operation
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=5 SRCH base="uid=*********,ou=Users,dc=osaka" scope=0 deref=0 filter="(objectClass=inetOrgPerson)"
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=5 SRCH attr=displayname telephonenumber mail
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=5 SEARCH RESULT tag=101 err=0 nentries=1 text=
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 op=6 UNBIND
Mar 16 14:38:09 osaka slapd[1390]: conn=3808 fd=26 closed

The last search that is performed over OpenLdap, is the value configured on Realms -> MyLdapRealm -> Search Configuration -> Lookup Attributes

Before the java exception the log displays the correct values from the openldap. Could someone bring some help to this issue, since I have not any way to see what is going on here?

Regards,
Andres de Barbara

Edited by: adebarbara on 16-mar-2011 16:15
  • 1. Re: Oracle OnTrack Ldap Realm Problem.
    drabe Newbie
    Currently Being Moderated
    Hi Andres,

    When On Track is first installed, it is configured to not be available to any end-users. This gives the admin an opportunity to finish the system configuration (such as LDAP setup) before opening it up to users. The message "The Application is closed at the current time" indicates that you have not yet opened the system to users. To do so, use the admin console (https://yourserver/ontrackAdmin), go to the "Application" settings, and change the "Application Status" from "Closed" to "Open".

    Hope that helps,

    --Dan                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               
  • 2. Re: Oracle OnTrack Ldap Realm Problem.
    415983 Newbie
    Currently Being Moderated
    Hi,

    As Dan has pointed out the issue you are seeing is not related to your LDAP set-up and glad that his solution resolved your issue.

    However please note that OpenLdap is not certified with On Track (please check in metalink for cert details). This means that OpenLdap has not been through QA and Oracle support would not be able to assist you with any OpenLdap specific issues.

    We do have support for OpenLdap on our roadmap, if you are planning to use this environment for production purposes, please update this thread with your timelines.

    Regards

    Reza Rokni Oracle On Track PM

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points