When i'm trying to Connect to the ejb on Oracle 10gAS (v10.1.2) from a standalone java client, i'm getting the following exception...
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Invalid username/password for cor (ias_admi n); nested exception is: javax.naming.AuthenticationException: Invalid username/password for cor (ias_admin) [Root exception is javax.naming.A uthenticationException: Invalid username/password for cor (ias_admin)] at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:153)
Scenario: I've two machinces m-1 and m-2. In m-1 Oracle 10g Infrastructure installed. In m-2 my application installed and it points to the OID in m-1 From standalone java client when i'm trying to connect the application on m-2 i'm getting authenticiation exception. But i'm able to login to the application on m-2 with the same userid/password.
"rajaramesh_m", We are please to have you with us here in the Oracle forum. Note that we require proper names. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.
In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.
The way you signed your name "Raja Ramesh Kumar" would be fine.
Raja, Oracle Application Server uses two types of security:
The default is JAZN -- in which case using principals (like you are in the code you posted) is incorrect. I only use OC4J stand-alone (as opposed to Oracle Application Server), so I only know how to configure use of principals (as opposed to JAZN) for OC4J stand-alone.
If your Oracle Application Server is configured to use principals, then the error message you are getting seems clear: you are either supplying an incorrect username and/or password.
Would it help if I told you to RTFM? Or have you already done that? For your information, it is available from: