The JMS Server Security Service was unable to authenticate USERID:ASDF

How to troubleshoot error messages that occur in the WebSphere Portal server v5.1.x log after security is enabled "The JMS Server Security Service was unable to authenticate UserID: Asdf ".
Document #: 1897475j09000

Body:
Title
How to troubleshoot error messages that occur in the WebSphere Portal server v5.1.x log after security is enabled "The JMS Server Security Service was unable to authenticate UserID: Asdf ".

Environment: (Product, platform, model, software version, etc.)

Product: WebSphere Portal Server
Version: 5.1.0, 5.1.0.1
Platform: Platform agnostic

Problem Description:
After security is enabled, the following error message appears in the WebSphere Portal Server v5.1.x log:

[6/2/05 15:01:29:378 EDT] 6b90ee23 jmssecurityse E msgs0508e:the JMS Server Security Service was unable to authenticate u Serid:asdf

[6/2/05 15:01:29:528 EDT] 707f6e21 freepool E j2ca0046e:method Createmanagedconnctionwithmcwrapper caught an exception du Ring creation of the managedconnection for resource jms/bpecf, throwing resourceallocationexception. Original Exception:javax.resource.spi.ResourceAdapterInternalException:createQueueConnection failed

Javax.jms.JMSSecurityException:MQJMS2013:invalid Security authentication supplied for Mqqueuemanager

Mqje027:queue Manager Security exit rejected connection with error code 23

[6/2/05 15:01:29:768 EDT] 707f6e21 mdblistenerim W wmsg0019e:unable to start MDB Listener Processcontainer mdb, jmsdestin ation jms/bpeintqueue:javax.jms.jmssecurityexception:mqjms2013:invalid Security Authentication supplied for Mqqueuemanager

[6/2/05 15:01:29:818 EDT] 707f6e21 msglistenerpo W wmsg0049e:failed to start MDB Processcontainer mdb against listener PO RT Bpeinternallistenerport

Answer:
This is because the user information for the JMS resource is not configured correctly, follow these steps:

1. Create a login user name of ASDF, give the password, for example Run2fast

2. Start Server1 and go to the management console:

Security-〉jaas configuration, j2c authentication data-〉<node>/bpeauthdataaliasemb_<node>_server1, modify user name asdf, password is run2fast

(<node> is the node name where Server1 is located)

3. Modify the <washome>/config/cells/<cell>/integral-jms-authorizations.xml file to add <userid>asdf</ Userid>, for example:

<queue-admin-userids>
<userid>asdf</userid>
</queue-admin-userids>

4. (Wmmur only) Add the ASDF user to the console administrative user, and then include a line in the <wpshome>/wmm/wmmwasadmin.xml file:

<admin logonid= "asdf" logonpassword= "afacwlqg1trlbnupqsppiw==" uniqueuserid= "uid=asdf,ou=people,dc=raleigh,dc= Ibm,dc=com "/>

The cryptographic string afacwlqg1trlbnupqsppiw== of the password Run2fast is generated by the run <wpshome>/config/work/wmm/bin/wmm_encrypt.bat (. sh)

5. Restart Server1

Note: You can use other legitimate users instead of ASDF