Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

LTPAServerObj E SECJ0369E: Authentication failed when using LTPA. The exception is .

5,700 views
Skip to first unread message

bajaj_...@hotmail.com

unread,
Jul 25, 2005, 6:11:47 PM7/25/05
to
I had websphere and portal working with wmmdb security and security was enabled.

I switched the user repository to ldap and execute the task
WPSconfig.sh enable-security-wmmur-ldap

and all hell breaks loose and now I can not even startup server1 leave alone the websphere_portal.
I am using WPS 5.1.0.1 on RH ES3

Any idea, what can I do to recover/solve the problem.

The error from SysteOut.log says
LTPAServerObj E SECJ0369E: Authentication failed when using LTPA. The exception is .

Maik Weber

unread,
Jul 26, 2005, 3:59:44 AM7/26/05
to
You have to check the output of the config task at first -- if something
got wrong.

Then check your wpconfig.properties if it contains the right values.

For more experts, you can disable security by editing security.xml. In
that case at least server1 should be started up again. Then you can have
a look on the configuration using the AdminConsole.

What exactly do you mean with wmmdb security ? Did you only used the
cloudscape initial installation ? Usually the command for setting up
LDAP connection is

WPSconfig.sh enable-security-ldap


Maik

bajaj_...@hotmail.com

unread,
Jul 26, 2005, 9:29:44 AM7/26/05
to
Following is the sequence of events
- Migrate from cloudscape to oracle
(./WPSconfig.sh database-transfer)
- switch to wmmur (and enable security) using the tasks
(./WPSconfig.sh enable-security-wmmur-db
)
- try to switch wmmur (LDAP with realm support) to ldap using the task
(./WPSconfig.sh enable-security-wmmur-ldap)

The last step breaks. I executed the validate-wmmur-ldap, which verified the connections and confid for ldap.

You mentioned I can edit the server.xml to get rid of the server1 security, can you point me to how to do this?

rgds,
deepak

CHANDRASEKARAN

unread,
Jul 26, 2005, 12:28:24 PM7/26/05
to
Dont be upset. working in WPS is challenging job

Back to your question, What version of LDAP server are you using. You
need to give proper user mappings, otherwise it will fail. Give me the
complete environment details.

Are you configured security sucessfully? I am sure that you are stuck
in action-create-deployment-credentials? I am sure you are missing some
LDAP configuration

Post me your message.

Maik Weber

unread,
Jul 28, 2005, 3:55:12 AM7/28/05
to
You can disable the security by editing
/opt/WebSphere/AppServer/config/cells/<nodename>/security.xml

Just set in the security tag the attribute "enabled" to false. It is the
first occurence of the attribute "enabled" -- ignore the others.

Maik

yomgui666

unread,
Nov 18, 2005, 12:01:29 PM11/18/05
to
You do a enable-security-wmmur-db and then a enable-security-wmmur-ldap task one after the other.

You should be doing one or the other.

Try to run the disable-security task and enable-security-wmmur-ldap task again

frode...@idscandinavia.com

unread,
Sep 6, 2006, 1:57:50 AM9/6/06
to
I have the same problem as you describes. I tried to set useLocalSecurityServer="false" to in security.xml, but no change. Did you ever found a soloution?

jaya.i...@gmail.com

unread,
Jun 4, 2007, 7:04:53 AM6/4/07
to
When my Portal Server (Security configured) access the AppServer(Security Not Configured) through the Portal Service ,I do get the same exception.

I do get the same exception.

com.ibm.ws.wmm.ldap.LdapBeanImpl authenticate(String DN, String pwd) The following Naming Exception occured during processing: "javax.naming.CommunicationException:

Inorder to solve this should i disable the Security in Portal Server or to enable Security in AppServer

shank...@aetna.com

unread,
Aug 27, 2007, 5:19:21 PM8/27/07
to
I got past this issue by simply bouncing the Deployment manager. I had bounced the nodeagent before but on coming up it complained that it is not able to sync with the DM. I looked at the DM logs and found LTPA related errors. SECJ0369E. Bouncing the DM did it for me. If you look at LTPA settings there is a timeout parm that you can set larger than the cache timeout in the global settings under security. That could be your permanant fix.
0 new messages