Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem:
OWSM integration with OID is not working while trying to configure Oracle Web Services Manager ( OWSM ) 10.1.3 to use the LDAP Authenticate Policy Step for a registered service to allow for authentication of a user using Oracle Internet Directory ( OID )
WARNING [AJPRequestHandler-RMICallHandler-15] ldap.LDAPAuthenticatorStep - Could not get DN for the userid: deg-syncdispatch-user
The gateway.log file:
--------------------------------
2009-09-02 09:39:18,103 WARNING [Thread-15] configuration.PolicySetWatchdog - Failed to retrieve policy set from policy manager with url http://mirsal2.dubaitrade.ae:80/policymanager/services/RegistrationService: com.cfluent.policymanager.sdk.base.exception.ServerException: org.xml.sax.SAXException: Bad envelope tag: HTML
2009-09-02 09:39:18,106 FINEST [Thread-15] configuration.PolicySetWatchdog - Failed to retrieve policy set from policy manager with url http://mirsal2.dubaitrade.ae:80/policymanager/services/RegistrationService
com.cfluent.policymanager.sdk.base.exception.ServerException: org.xml.sax.SAXException: Bad envelope tag: HTML
at com.cfluent.policymanager.sdk.client.soap.SoapComponentConfigurator.getUpdatedPolicies(SoapComponentConfigurator.java:229)
at com.cfluent.agent.configuration.PolicySetWatchdog.getPolicySetFromPolicyManager(PolicySetWatchdog.java:168)
at com.cfluent.agent.configuration.PolicySetWatchdog.pollFromPolicyManager(PolicySetWatchdog.java:205)
at com.cfluent.agent.configuration.PolicySetWatchdog.run(PolicySetWatchdog.java:91)
2009-09-02 09:41:18,123 FINEST [Thread-15] configuration.PolicySetWatchdog - Checking Policy Manager
2009-09-02 09:41:18,133 WARNING [Thread-15] configuration.PolicySetWatchdog - Failed to retrieve policy set from policy manager with url http://mirsal2.dubaitrade.ae:80/policymanager/services/RegistrationService: com.cfluent.policymanager.sdk.base.exception.ServerException: org.xml.sax.SAXException: Bad envelope tag: HTML
2009-09-02 09:41:18,133 FINEST [Thread-15] configuration.PolicySetWatchdog - Failed to retrieve policy set from policy manager with url http://mirsal2.dubaitrade.ae:80/policymanager/services/RegistrationService
com.cfluent.policymanager.sdk.base.exception.ServerException: org.xml.sax.SAXException: Bad envelope tag: HTML
at com.cfluent.policymanager.sdk.client.soap.SoapComponentConfigurator.getUpdatedPolicies(SoapComponentConfigurator.java:229)
at com.cfluent.agent.configuration.PolicySetWatchdog.getPolicySetFromPolicyManager(PolicySetWatchdog.java:168)
at com.cfluent.agent.configuration.PolicySetWatchdog.pollFromPolicyManager(PolicySetWatchdog.java:205)
at com.cfluent.agent.configuration.PolicySetWatchdog.run(PolicySetWatchdog.java:91)
In the policymanager.log file of N2:
---------------------------------------------
com.cfluent.utils.db.DBException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=pdppdb03-vip.dubaiworld.ae)(PORT=1750))(ADDRESS=(PROTOCOL=TCP)(HOST=pdppdb04-vip.dubaiworld.ae)(PORT=1750))(CONNECT_DATA=(SERVICE_NAME=PSOA.dubaiworld.ae)))
at com.cfluent.utils.db.DBContext.getConnection(DBContext.java:95)
at com.cfluent.db.registry.ComponentsTable.isActiveComponent(ComponentsTable.java:323)
at com.cfluent.policymanager.da.ComponentAccessor.isValidComponent(ComponentAccessor.java:267)
at com.cfluent.policymanager.service.policy.PolicyQuery.getComponentPolicySet(PolicyQuery.java:52)
at com.cfluent.policymanager.service.soap.RegistrationService.getUpdatedPolicies(RegistrationService.java:192)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:402)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:309)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:333)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:481)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:323)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:854)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=pdppdb03-vip.dubaiworld.ae)(PORT=1750))(ADDRESS=(PROTOCOL=TCP)(HOST=pdppdb04-vip.dubaiworld.ae)(PORT=1750))(CONNECT_DATA=(SERVICE_NAME=PSOA.dubaiworld.ae)))
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:280)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:361)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:595)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:48)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:175)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.cfluent.utils.db.DBContext.getConnection(DBContext.java:86)
... 31 more
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
In the gateway.log of N1:
--------------------------------------
2009-09-02 09:23:23,010 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Found the UsernameToken Header
2009-09-02 09:23:23,010 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Element Value:deg-syncdispatch-user
2009-09-02 09:23:23,011 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Element Value:plvSdpOQ1
2009-09-02 09:23:23,011 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Successfully retrieved username and password
2009-09-02 09:23:23,011 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Removing the UsernameToken Header
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] CSWComponent - Executing policy step. Policy='SID0003009', Step Name='LDAP Authenticate', Step Class='com.cfluent.policysteps.security.ldap.LDAPAuthenticatorStep'
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] common.AbstractAuthenticatorStep - Step LDAP Authenticate called
2009-09-02 09:23:23,011 FINEST [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - Inside LDAP authenticate
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - Getting DN for user deg-syncdispatch-user
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - BaseDN=cn=Users,dc=DT,dc=tco,dc=co,dc=ae
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - Filter=(&(uid=deg-syncdispatch-user)(objectclass=inetOrgPerson))
2009-09-02 09:23:23,012 INFO [AJPRequestHandler-RMICallHandler-5] ldap.DirContextHolder - Attempt 1 to connect
2009-09-02 09:23:23,018 WARNING [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - Could not get DN for the userid: deg-syncdispatch-user
2009-09-02 09:23:23,028 FINEST [MessageLogWriterDaemon] util.BoundedTaskQueue - Removing from bounded queue AsyncMessageLog
2009-09-02 09:23:23,053 FINE [AJPRequestHandler-RMICallHandler-5] CSWComponent - Step execution failed: Fault Code=[http://schemas.oblix.com/ws/2003/08/Faults/AuthenticationFault] Fault String=[Unable to authenticate user deg-syncdispatch-user against LDAP Server.] Policy=[SID0003009] Pipeline=[Request] Step Name=[LDAP Authenticate] Step Class=[com.cfluent.policysteps.security.ldap.LDAPAuthenticatorStep]
2009-09-02 09:23:23,053 FINER [AJPRequestHandler-RMICallHandler-5] common.PrepareForServiceStep - Step PrepareForServiceStep called
2009-09-02 09:23:23,053 FINEST [AJPRequestHandler-RMICallHandler-5] wssecurity.WSSecurityUtils - Found the Security Header
2009-09-02 09:23:23,053 FINEST [AJPRequestHandler-RMICallHandler-5] wssecurity.WSSecurityUtils - Removing the Security Header
2009-09-02 09:23:23,053 FINE [AJPRequestHandler-RMICallHandler-5] gateway.Invoker - Result of Request Pipeline is 1
2009-09-02 09:23:23,053 FINEST [AJPRequestHandler-RMICallHandler-5] agent.AgentRuntime - Released read lock
2009-09-02 09:23:23,054 FINEST [AJPRequestHandler-RMICallHandler-5] listener.ProtocolListener - Request message size: 1,100
2009-09-02 09:23:23,054 FINEST [AJPRequestHandler-RMICallHandler-5] listener.ProtocolListener - Response message size: 380
2009-09-02 09:23:23,055 FINEST [AJPRequestHandler-RMICallHandler-5] policysteps.CoremanClient - creating invocation measurement with serviceStatus=-1, invocationstatus=1, componentId=C0003001
2009-09-02 09:23:23,055 FINEST [AJPRequestHandler-RMICallHandler-5] util.BoundedTaskQueue - adding to bounded queue
2009-09-02 09:23:23,055 FINEST [AJPRequestHandler-RMICallHandler-5] agent.AgentRuntime - Released read lock
2009-09-02 09:23:23,301 FINEST [Thread-18] util.BoundedTaskQueue - Removing from bounded queue
2009-09-02 09:23:23,301 FINEST [Thread-18] policysteps.CoremanClient - initInternal called
2009-09-02 09:23:23,303 WARNING [Thread-18] policysteps.CoremanClient - Fail to connect to coreman, Could not get RMI ICoremanAdaptor
2009-09-02 09:23:23,303 FINEST [Thread-18] policysteps.CoremanClient - Fail to connect to coreman
com.cfluent.coreman.sdk.CoremanException: Could not get RMI ICoremanAdaptor
at com.cfluent.coreman.sdk.client.CoremanAdaptorFactory.getRMIClient(CoremanAdaptorFactory.java:70)
at com.cfluent.coreman.sdk.client.CoremanAdaptorFactory.getCoremanAdaptor(CoremanAdaptorFactory.java:86)
at com.cfluent.policysteps.CoremanClient.initInternal(CoremanClient.java:87)
at com.cfluent.policysteps.CoremanClient.sendMeasurementsInternal(CoremanClient.java:251)
at com.cfluent.policysteps.CoremanClientDaemon.sendMeasurements(CoremanClient.java:356)
at com.cfluent.policysteps.CoremanClientDaemon.run(CoremanClient.java:307)
target exception:
java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused (errno:239)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
at java.rmi.Naming.lookup(Naming.java:84)
at com.cfluent.coreman.sdk.client.CoremanAdaptorFactory.getRMIClient(CoremanAdaptorFactory.java:67)
at com.cfluent.coreman.sdk.client.CoremanAdaptorFactory.getCoremanAdaptor(CoremanAdaptorFactory.java:86)
at com.cfluent.policysteps.CoremanClient.initInternal(CoremanClient.java:87)
at com.cfluent.policysteps.CoremanClient.sendMeasurementsInternal(CoremanClient.java:251)
at com.cfluent.policysteps.CoremanClientDaemon.sendMeasurements(CoremanClient.java:356)
at com.cfluent.policysteps.CoremanClientDaemon.run(CoremanClient.java:307)
Caused by: java.net.ConnectException: Connection refused (errno:239)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:530)
at java.net.Socket.connect(Socket.java:480)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:180)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
Troubleshooting:
If you get an error saying ldap.LDAPAuthenticatorStep - Could not get DN for the <user>, verify password using the ldapbind command on your OID instance.
Also, ensure the DN entry is correctly given in OWSM's LDAP configuration page.
Would you please refer to the section "Troubleshooting" in the provided Note 782989.1?
check that the user has already bound and the password is correct by the following command:
ldapbind -h <HOST> -p <PORT> -D "cn=<username>,cn=users,dc=<domain>" -w <PASSWORD>
You should receive the message "Bind Successful" .
Enable OWSM logs with increased debugging by the following Note:
Note.726219.1 <How To Change Log Level for Oracle Web Services Manager (OWSM)>.
Solution:
The cause is creating the OID user using the oidadmin tool and did not set the proper values for the attributes which can be associated with a user to be created.
In order to solve this issue, you have to drop the OID user and recreate it using oiddas
Reference:
WebIV SEARCH
------------------------
Note 782989.1 : <An Example Of Using LDAP Authenticate Step in OWSM to Authenticate a Registered Web Service to OID>
The above note is used to configure Oracle Web Services Manager ( OWSM ) 10.1.3 to use the LDAP Authenticate Policy Step for a registered service
to allow for authentication of a user using Oracle Internet Directory ( OID ).
OWSM integration with OID is not working while trying to configure Oracle Web Services Manager ( OWSM ) 10.1.3 to use the LDAP Authenticate Policy Step for a registered service to allow for authentication of a user using Oracle Internet Directory ( OID )
WARNING [AJPRequestHandler-RMICallHandler-15] ldap.LDAPAuthenticatorStep - Could not get DN for the userid: deg-syncdispatch-user
The gateway.log file:
--------------------------------
2009-09-02 09:39:18,103 WARNING [Thread-15] configuration.PolicySetWatchdog - Failed to retrieve policy set from policy manager with url http://mirsal2.dubaitrade.ae:80/policymanager/services/RegistrationService: com.cfluent.policymanager.sdk.base.exception.ServerException: org.xml.sax.SAXException: Bad envelope tag: HTML
2009-09-02 09:39:18,106 FINEST [Thread-15] configuration.PolicySetWatchdog - Failed to retrieve policy set from policy manager with url http://mirsal2.dubaitrade.ae:80/policymanager/services/RegistrationService
com.cfluent.policymanager.sdk.base.exception.ServerException: org.xml.sax.SAXException: Bad envelope tag: HTML
at com.cfluent.policymanager.sdk.client.soap.SoapComponentConfigurator.getUpdatedPolicies(SoapComponentConfigurator.java:229)
at com.cfluent.agent.configuration.PolicySetWatchdog.getPolicySetFromPolicyManager(PolicySetWatchdog.java:168)
at com.cfluent.agent.configuration.PolicySetWatchdog.pollFromPolicyManager(PolicySetWatchdog.java:205)
at com.cfluent.agent.configuration.PolicySetWatchdog.run(PolicySetWatchdog.java:91)
2009-09-02 09:41:18,123 FINEST [Thread-15] configuration.PolicySetWatchdog - Checking Policy Manager
2009-09-02 09:41:18,133 WARNING [Thread-15] configuration.PolicySetWatchdog - Failed to retrieve policy set from policy manager with url http://mirsal2.dubaitrade.ae:80/policymanager/services/RegistrationService: com.cfluent.policymanager.sdk.base.exception.ServerException: org.xml.sax.SAXException: Bad envelope tag: HTML
2009-09-02 09:41:18,133 FINEST [Thread-15] configuration.PolicySetWatchdog - Failed to retrieve policy set from policy manager with url http://mirsal2.dubaitrade.ae:80/policymanager/services/RegistrationService
com.cfluent.policymanager.sdk.base.exception.ServerException: org.xml.sax.SAXException: Bad envelope tag: HTML
at com.cfluent.policymanager.sdk.client.soap.SoapComponentConfigurator.getUpdatedPolicies(SoapComponentConfigurator.java:229)
at com.cfluent.agent.configuration.PolicySetWatchdog.getPolicySetFromPolicyManager(PolicySetWatchdog.java:168)
at com.cfluent.agent.configuration.PolicySetWatchdog.pollFromPolicyManager(PolicySetWatchdog.java:205)
at com.cfluent.agent.configuration.PolicySetWatchdog.run(PolicySetWatchdog.java:91)
In the policymanager.log file of N2:
---------------------------------------------
com.cfluent.utils.db.DBException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=pdppdb03-vip.dubaiworld.ae)(PORT=1750))(ADDRESS=(PROTOCOL=TCP)(HOST=pdppdb04-vip.dubaiworld.ae)(PORT=1750))(CONNECT_DATA=(SERVICE_NAME=PSOA.dubaiworld.ae)))
at com.cfluent.utils.db.DBContext.getConnection(DBContext.java:95)
at com.cfluent.db.registry.ComponentsTable.isActiveComponent(ComponentsTable.java:323)
at com.cfluent.policymanager.da.ComponentAccessor.isValidComponent(ComponentAccessor.java:267)
at com.cfluent.policymanager.service.policy.PolicyQuery.getComponentPolicySet(PolicyQuery.java:52)
at com.cfluent.policymanager.service.soap.RegistrationService.getUpdatedPolicies(RegistrationService.java:192)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:402)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:309)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:333)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:481)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:323)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:854)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=pdppdb03-vip.dubaiworld.ae)(PORT=1750))(ADDRESS=(PROTOCOL=TCP)(HOST=pdppdb04-vip.dubaiworld.ae)(PORT=1750))(CONNECT_DATA=(SERVICE_NAME=PSOA.dubaiworld.ae)))
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:280)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:361)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:595)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:48)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:175)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.cfluent.utils.db.DBContext.getConnection(DBContext.java:86)
... 31 more
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
In the gateway.log of N1:
--------------------------------------
2009-09-02 09:23:23,010 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Found the UsernameToken Header
2009-09-02 09:23:23,010 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Element Value:deg-syncdispatch-user
2009-09-02 09:23:23,011 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Element Value:plvSdpOQ1
2009-09-02 09:23:23,011 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Successfully retrieved username and password
2009-09-02 09:23:23,011 FINEST [AJPRequestHandler-RMICallHandler-5] security.WSBasicCredsExtractor - Removing the UsernameToken Header
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] CSWComponent - Executing policy step. Policy='SID0003009', Step Name='LDAP Authenticate', Step Class='com.cfluent.policysteps.security.ldap.LDAPAuthenticatorStep'
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] common.AbstractAuthenticatorStep - Step LDAP Authenticate called
2009-09-02 09:23:23,011 FINEST [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - Inside LDAP authenticate
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - Getting DN for user deg-syncdispatch-user
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - BaseDN=cn=Users,dc=DT,dc=tco,dc=co,dc=ae
2009-09-02 09:23:23,011 FINE [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - Filter=(&(uid=deg-syncdispatch-user)(objectclass=inetOrgPerson))
2009-09-02 09:23:23,012 INFO [AJPRequestHandler-RMICallHandler-5] ldap.DirContextHolder - Attempt 1 to connect
2009-09-02 09:23:23,018 WARNING [AJPRequestHandler-RMICallHandler-5] ldap.LDAPAuthenticatorStep - Could not get DN for the userid: deg-syncdispatch-user
2009-09-02 09:23:23,028 FINEST [MessageLogWriterDaemon] util.BoundedTaskQueue - Removing from bounded queue AsyncMessageLog
2009-09-02 09:23:23,053 FINE [AJPRequestHandler-RMICallHandler-5] CSWComponent - Step execution failed: Fault Code=[http://schemas.oblix.com/ws/2003/08/Faults/AuthenticationFault] Fault String=[Unable to authenticate user deg-syncdispatch-user against LDAP Server.] Policy=[SID0003009] Pipeline=[Request] Step Name=[LDAP Authenticate] Step Class=[com.cfluent.policysteps.security.ldap.LDAPAuthenticatorStep]
2009-09-02 09:23:23,053 FINER [AJPRequestHandler-RMICallHandler-5] common.PrepareForServiceStep - Step PrepareForServiceStep called
2009-09-02 09:23:23,053 FINEST [AJPRequestHandler-RMICallHandler-5] wssecurity.WSSecurityUtils - Found the Security Header
2009-09-02 09:23:23,053 FINEST [AJPRequestHandler-RMICallHandler-5] wssecurity.WSSecurityUtils - Removing the Security Header
2009-09-02 09:23:23,053 FINE [AJPRequestHandler-RMICallHandler-5] gateway.Invoker - Result of Request Pipeline is 1
2009-09-02 09:23:23,053 FINEST [AJPRequestHandler-RMICallHandler-5] agent.AgentRuntime - Released read lock
2009-09-02 09:23:23,054 FINEST [AJPRequestHandler-RMICallHandler-5] listener.ProtocolListener - Request message size: 1,100
2009-09-02 09:23:23,054 FINEST [AJPRequestHandler-RMICallHandler-5] listener.ProtocolListener - Response message size: 380
2009-09-02 09:23:23,055 FINEST [AJPRequestHandler-RMICallHandler-5] policysteps.CoremanClient - creating invocation measurement with serviceStatus=-1, invocationstatus=1, componentId=C0003001
2009-09-02 09:23:23,055 FINEST [AJPRequestHandler-RMICallHandler-5] util.BoundedTaskQueue - adding to bounded queue
2009-09-02 09:23:23,055 FINEST [AJPRequestHandler-RMICallHandler-5] agent.AgentRuntime - Released read lock
2009-09-02 09:23:23,301 FINEST [Thread-18] util.BoundedTaskQueue - Removing from bounded queue
2009-09-02 09:23:23,301 FINEST [Thread-18] policysteps.CoremanClient - initInternal called
2009-09-02 09:23:23,303 WARNING [Thread-18] policysteps.CoremanClient - Fail to connect to coreman, Could not get RMI ICoremanAdaptor
2009-09-02 09:23:23,303 FINEST [Thread-18] policysteps.CoremanClient - Fail to connect to coreman
com.cfluent.coreman.sdk.CoremanException: Could not get RMI ICoremanAdaptor
at com.cfluent.coreman.sdk.client.CoremanAdaptorFactory.getRMIClient(CoremanAdaptorFactory.java:70)
at com.cfluent.coreman.sdk.client.CoremanAdaptorFactory.getCoremanAdaptor(CoremanAdaptorFactory.java:86)
at com.cfluent.policysteps.CoremanClient.initInternal(CoremanClient.java:87)
at com.cfluent.policysteps.CoremanClient.sendMeasurementsInternal(CoremanClient.java:251)
at com.cfluent.policysteps.CoremanClientDaemon.sendMeasurements(CoremanClient.java:356)
at com.cfluent.policysteps.CoremanClientDaemon.run(CoremanClient.java:307)
target exception:
java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused (errno:239)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
at java.rmi.Naming.lookup(Naming.java:84)
at com.cfluent.coreman.sdk.client.CoremanAdaptorFactory.getRMIClient(CoremanAdaptorFactory.java:67)
at com.cfluent.coreman.sdk.client.CoremanAdaptorFactory.getCoremanAdaptor(CoremanAdaptorFactory.java:86)
at com.cfluent.policysteps.CoremanClient.initInternal(CoremanClient.java:87)
at com.cfluent.policysteps.CoremanClient.sendMeasurementsInternal(CoremanClient.java:251)
at com.cfluent.policysteps.CoremanClientDaemon.sendMeasurements(CoremanClient.java:356)
at com.cfluent.policysteps.CoremanClientDaemon.run(CoremanClient.java:307)
Caused by: java.net.ConnectException: Connection refused (errno:239)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:530)
at java.net.Socket.connect(Socket.java:480)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:180)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
Troubleshooting:
If you get an error saying ldap.LDAPAuthenticatorStep - Could not get DN for the <user>, verify password using the ldapbind command on your OID instance.
Also, ensure the DN entry is correctly given in OWSM's LDAP configuration page.
Would you please refer to the section "Troubleshooting" in the provided Note 782989.1?
check that the user has already bound and the password is correct by the following command:
ldapbind -h <HOST> -p <PORT> -D "cn=<username>,cn=users,dc=<domain>" -w <PASSWORD>
You should receive the message "Bind Successful" .
Enable OWSM logs with increased debugging by the following Note:
Note.726219.1 <How To Change Log Level for Oracle Web Services Manager (OWSM)>.
Solution:
The cause is creating the OID user using the oidadmin tool and did not set the proper values for the attributes which can be associated with a user to be created.
In order to solve this issue, you have to drop the OID user and recreate it using oiddas
Reference:
WebIV SEARCH
------------------------
Note 782989.1 : <An Example Of Using LDAP Authenticate Step in OWSM to Authenticate a Registered Web Service to OID>
The above note is used to configure Oracle Web Services Manager ( OWSM ) 10.1.3 to use the LDAP Authenticate Policy Step for a registered service
to allow for authentication of a user using Oracle Internet Directory ( OID ).
No comments:
Post a Comment