wood burning stoves 2.0*
The moose likes Websphere and the fly likes Webshpere security exception Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Webshpere security exception" Watch "Webshpere security exception" New topic
Author

Webshpere security exception

Kirthana Traj
Greenhorn

Joined: Apr 13, 2011
Posts: 2
Hi,
I have currently installed websphere 7.0.1 on windows 2003 system. I have created a Queue manager and created default queues and topics. When I try to do a send of messages i get the following exception
<description>javax.jms.JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager</description>
# ------------------------------------------------------------
# IBM Websphere MQ Support for Java Message Service
# This is the default configuration file for the Websphere MQ Classes for
# Java Message Service Administration Tool.
#
# <N_OCO_COPYRIGHT>
# Licensed Materials - Property of IBM
#
# 5724-H72, 5655-R36, 5724-L26, 5655-L82
#
# (c) Copyright IBM Corp. 2008 All Rights Reserved.
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with
# IBM Corp.
# <NOC_COPYRIGHT>
# ------------------------------------------------------------
#
# The following line specifies which JNDI service provider is in use.
# It currently indicates an File System Context. If a different
# service provider is used, this line should be commented out and the
# appropriate one should be uncommented.
#
# com.sun.jndi.fscontext.RefFSContextFactory is the FileSystem JNDI Context
#
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
#
# The following line specifies the URL of the service provider's initial
# context. It currently refers to an File System Context. Examples of a
# LDAP root context URL and WebSphere's JNDI namespace are also shown, commented
# out.
#
#PROVIDER_URL=ldap://localhost/o=ibm,c=us
PROVIDER_URL=file:/C:/JNDI-Directory
#PROVIDER_URL=iiop://localhost/
#
# The following line specifies the security authentication model in use,
# and may be 'none' (for anonymous authentication), 'simple', or 'CRAM_MD5'.
#
SECURITY_AUTHENTICATION=none
#
# If you don't have SECURITY_AUTHENTICATION=none, then JMSAdmin will
# prompt you for the User DN and password. If you want to bypass these
# prompts then you can specify one or both of the values here. Since
# the password here is in cleartext this is not normally recommended
# except for testing. You should replace these values with your own.
#
#PROVIDER_USERDN=cn=Manager,o=ibm,c=uk
#PROVIDER_PASSWORD=secret
#
#
# The following line determines whether to use an InitialDirContext, or an
# InitialContext. Takes value of TRUE or FALSE.
#USE_INITIAL_DIR_CONTEXT=TRUE
#
# The following line specifies a prefix to add to names when carrying out operations such
# as lookup/bind.
#NAME_PREFIX=cn=
#
# The following line specifies a marker at which names will be truncated when viewing
# the contents of the Context.
#NAME_READABILITY_MARKER=..
#
# The three standard types of InitialContextFactory have the following defaults;
# Note that these defaults will be set automatically if the flags are not present, but
# will be overrided by including the flags.
#
# LDAP FSCONTEXT WEBSPHERE
# ------------------------------------------------------------------------------------
# USE_INITIAL_DIR_CONTEXT TRUE FALSE FALSE
# NAME_PREFIX cn= omitted omitted
# NAME_READABILITY_MARKER omitted omitted ..
#


This is the JMSadmin.config file help me.....
Anant Rao
Ranch Hand

Joined: Nov 12, 2004
Posts: 126
Looks like the id you are using cannot be authenticated. Check the password or the privilges on the queue.

Thanks
Kirthana Traj
Greenhorn

Joined: Apr 13, 2011
Posts: 2
How can i chk the security and permissions of the queue.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Webshpere security exception
 
Similar Threads
what is the Need of MyAdmin.config when integrating MQ with BEA WebLogic server
JMS in WAS 4.0
JNDI initialisation failed, please check your JNDI settings and service
Configure a Bridge between Websphere MQ 6.0(Previously MQSeries) and Weblogic 9.2
Can JMS + MQ work together?