SDS + Jboss JMS authentication

Similar Questions

• JBoss 7 and authentication of BlazeDS

  Hello

  Does anyone tried to set up the authentication database and BlazeDS if JBoss 7?

  I did the steps that I've used with other versions but still get the usual error;

  "There was a failure not managed on the server. Flex, messaging, security, TomcatLoginHolder '

  The truth is that I feel like I'm stubbling autour in obscurity because JBoss 7 is so different to previous versions.

  Any help would be appreciated

  I found the answer to this effect;

  Boredom, I had set the tomcat valve in JBoss 7. Previously, this was done in the tomcat configuration files and is documented in BlazeDS docs.

  Now, the configuration is created by;

  (1) put flex-tomcat-.jar and flex-tomcat - server.jar in the WEB-INF/lib of your blazeds war file and in the same war

  (2) in your jboss - Web.XML under WEB - INF the following content

  yourSecurityDomain

  flex.messaging.security.TomcatValve

  The blazeds configuration remains the same.

• Form of authentication issues - from attributes to applications on JBoss

  Question: How do I pass the user name, password and all other attributes that I draw from my login form in an application for SINGLE sign-on when the authenticated user?
  
  My environment is a server Apache 2.2 protected with the WebGate using a reverse proxy to JBoss application server.
  
  Once authenticated, how I pass the name to username/password / other attributes for applications on my JBoss server?
  
  Thank you.
  Bryan

  Bryan,

  You will find [this response | http://forums.oracle.com/forums/message.jspa?messageID=3446719#3446719] useful Kiran. A few comments-

  (1) HTTP_OBLIX_UID is a name of special header used by the OAM identity system. I advise you to not use that to rule out the possibility of confusion.

  (2) I knew the type of action to be case-sensitive. Instead of HEADERVAR, you might want to try HeaderVar. In addition, if you use a Cookie, you should see the value of the DN even in subsequent requests in HTTP traces

  (3) If you want to stick with headers, you can put a simple jsp page on your JBoss server and have as the protected resource. You should be able to print the received headers in the jsp page.

  -Vinod

• Is it possible to require SSL connection for a JMS resource?

  Hi, I'm working on OSB 12.1.3 and I'm dealing with JMS resources.

  Since in our landscape, that these resources will also be used by external customers personalized, I added a few security policies to restrict access of the user, so I get authentication and authorization covered.

  I can't find enough information on the chain securing T3s on Protocol: T3s is present and functional, but I couldn't find a way to make it compulsory in WLS.

  Any help would be appreciated

  Christian

  Christian,

  According to my knowledge, weblogic doesn't provide us with that ability that access you resources on the managed server ports. So ideally when you disable this listening port and enable the ssl port, then it would have an impact on all resources. The possible means of blocking custom external clients access the jms resources to firewall rules.

• TimesTen - 7001: user authentication failed when using XLA

  I installed TimesTen 11.2.1.8.0 on AIX 5.3 System.* user 'oracle '. I created another user of the application 'risk' to use in my application with TimesTen.

  When running my application with the user 'risk' to connect with TimesTen it is OK. But when I want to use the XLA feature, when I call the createDurableSubscriber function, it returns the error

  javax.jms.JMSException: failure of SQLDriverConnect (XlaCommon.c, line 48): S1000 7001 [TimesTen] [driver ODBC of TimesTen 11.2.1.8.0] TT7001 [TimesTen]: user authentication failed - file "db.c", lineno 9722, procedure 'sbDbConnect '.

  It is strange that if I switch to user 'oracle', it works fine.

  Can someone please help understand the reason why.

  Thank you

  You created the user 'at risk' within your TimesTen database?

  CREATE a USER risk IDENTIFIED BY 'some password'?

  You granted the privilege of the user risk to use XLA?

  XLA GRANT at risk;

  Have you used this user name and password in the JDBC URL when connecting to the database application JMS/XLA?

  The 'oracle' user is probably your admin user of the instance (which is the database root) and therefore can use all the features without special action (but of course you never run application as that user).

  Chris

• HTTP authentication support - is STILL Basic Plugin

  I am trying to make a connection IS with a host in the inventory of the VCO plugin. The connection request returns an authorization token in the response header that is then defined as a header in all subsequent REST calls in VCO. I am able to make the connection and authorization token in the response header in the browser based REST clients. However if I do the same connect REST in VCO call apparently remove the response header as response.getHesders () for the connect call will return null.

  It seems that the authorization in the HTTP-REST plugin is handled differently, I would like to know how to make a connection with the plugin HTTP and REST. The REST API that I'm trying to interface with has a connection like this operation.

  DOWNLOAD/login

  Request

  GET https://192.168.1.10:4534 / connection

  Headers

  Content-Type: application/xml

  Permission: Base64EncodedString base composed of 'name '.
  

  Response

  Headers

  X SDS-AUTH-TOKEN: < AUTH_TOKEN >

  Body

  HTTP/1.1 200 OK

  Content-Type: application/xml

  <? XML version = "1.0" encoding = "UTF-8" standalone = "yes"? >

  < loggedIn >

  < user > user name < / user >

  < / loggedIn >

  How can I access this authentication token in VCO? Is - this accassable through the REST-host?

  I also tried to set up the host in the HTTP-REST plugin with basic authentication and a session mode of "by the Session of the user", but I'm not sure how to pass the user name and password to the host when using this type of session.

  Thank you

  slahy

  I found an example to access the headers in the link below, and it seems that you must place the answer in a variable to access the content of the response. Seems a little odd to me, but it works.

  var SessionResponse = new Properties ();

  SessionResponse.put ("statusCode", CreateSession.statusCode);

  SessionResponse.put ("headers", CreateSession.getAllHeaders ());

  If (SessionResponse.statusCode == "200") {}

  System.log ("created successful logon")

  xZertoSessionKey = SessionResponse.headers.get ("x-zerto-session")

  }

  else {}

  System.log ("Session could not be established")

  }

  http://www.vcoportal.de/2014/06/automate-your-zerto-disaster-recovery-solution-with-VCO/

• JBoss.mq:service = MessageCache is not registered

  Greetings,
  
  CentOS fresh install with JBoss 4.0.5, HQ Agent 4.0.3. Everything has been discovered late, not to mention that JBoss. Even if it comes in resources-server, it displays an error:
  
  The configuration has not been set for this resource due to: invalid configuration: error recovery value: metric not found [jboss.mq:service=MessageCache:CacheHits:java.naming.provider.url=jnp%3A//127.0.0.1%3A1099,java.naming.security.principal=***,java.naming.security.credentials=***]: javax.management.InstanceNotFoundException: jboss.mq:service = MessageCache is not registered.
  
  
  I can't update the credentials for the JMX console via the web interface, it continues to run above error at home.
  
  Does anyone have an idea what causes this? I have a little more with JBoss 4.x servers where I don't have this problem. (jboss installation is identical on all servers).
  
  I looked around for "MessageCache is not registered" and similar variations, can not really find something useful that would help me to get back on the right track. I don't really know if the problem is with the Hyperic Agent, JBoss, something else?
  
  Thank you
  
  Post edited by: uniwiz

  Hello

  Try the following steps:

  Go to the Administration tab-> default Configuration monitoring
  Do scroll to JBoss 4.x and disable metric collection for JMS Message Cache according to the Manual:

  http://support.Hyperic.com/display/doc/monitoring+defaults+configuration

  Then try to set up the configuration of the resource.

  See you soon,.
  Mirko

• JCA on JBoss

  Hello
  
  I took several days, setting up connection between jboss and tuxedo by jca, but I only have TPENOENT.
  
  Here's my configuration files
  
  RA. XML
  
  + <? XML version = "1.0" encoding = "UTF-8"? > +.
  + < xmlns = "http://java.sun.com/xml/ns/j2ee" + connector
  xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance".
  xsi: schemaLocation = "http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd".
  version = "1.5" >
  + JCA Tuxedo adapter < display name > < / name >.
  + Oracle < vendor name > - < / vendor name > +.
  + Tuxedo < eis-type > < / eis-type > +.
  + resourceadapter < version > 11gR 1 (11.1.1.2.1) < / resourceadapter-version > +.
  + < license > +.
  + license < description > Tuxedo salt < / description >.
  + license-required > < false < / license-required > +.
  + < / license > +.
  + < resourceadapter > +.
  + > class resourceadapter < com.oracle.tuxedo.adapter.TuxedoResourceAdapter < / resourceadapter class > +.
  + < config-property > +.
  + traceLevel < config-property-name > < / config-property-name > +.
  + java.lang.String < config-property-type > < / config-property-type > +.
  + < config-property-value > 80000 < / config-property-value > +.
  + < / config-property > +.
  + < config-property > +.
  + < config-property-name > xaAffinity < / config-property-name > +.
  + java.lang.String < config-property-type > < / config-property-type > +.
  + < config-property-value > true < / config-property-value > +.
  + < / config-property > +.
  + < config-property > +.
  + dmconfig < config-property-name > < / config-property-name > +.
  + java.lang.String < config-property-type > < / config-property-type > +.
  + < config-property-value > /export/home/jboss/jboss/standalone/configuration/dmconfig.xml < / config-property-value > +.
  + < / config-property > +.
  + < outgoing resourceadapter - > +.
  + connection < definition > +.
  + class < managedconnectionfactory > com.oracle.tuxedo.adapter.spi.TuxedoManagedConnectionFactory < / managedconnectionfactory-class > +.
  + > connectionfactory interface < javax.resource.cci.ConnectionFactory < / connectionfactory interface > +.
  + com.oracle.tuxedo.adapter.cci.TuxedoConnectionFactory < connectionfactory-impl-class > < / connectionfactory-impl-class > +.
  + connection < interface > javax.resource.cci.Connection < / interfaces > +.
  + connection < impl-class > com.oracle.tuxedo.adapter.cci.TuxedoJCAConnection < / connection-impl-class > +.
  + < / connection-definition > +.
  + < transaction-support > LocalTransaction < / transaction-support > +.
  + < authentication mechanism - > +.
  + BasicPassword <-authentication mechanism-type > < / type of authentication mechanism > +.
  + > interface credential < javax.resource.spi.security.PasswordCredential < / credential-interface > +.
  + < / authentication mechanism > +.
  + fake > helps reauthentication < < / re-authentication-support > +.
  + < / outgoing-resourceadapter > +.
  + < / resourceadapter > +.
  + < / connector > +.
  
  Dmconfig. XML
  
  + <? XML version = "1.0" encoding = "UTF-8"? > < TuxedoConnector > +.
  + < name LocalAccessPoint = "JDOM" > +.
  + < AccessPointId > JDOM1 < / AccessPointId > +.
  + < NetworkAddress > //maqueta2:5001 < / NetworkAddress > +.
  + < / LocalAccessPoint > +.
  + < name RemoteAccessPoint = "TDOM" > +.
  + < AccessPointId > TDOM1 < / AccessPointId > +.
  + < NetworkAddress > //maqueta2:5000 < / NetworkAddress > +.
  + < / RemoteAccessPoint > +.
  + < SessionProfile name = "profile_1" > +.
  + < security > NO < / security > +.
  + < period > 30000 < / period > +.
  + < interoperate > false < / interfonctionnent > +.
  + < ConnectionPolicy > ON_STARTUP < / ConnectionPolicy > +.
  + local < ACLPolicy > < / ACLPolicy > +.
  + local < CredentialPolicy > < / CredentialPolicy > +.
  + < > 60 RetryInterval < / RetryInterval > +.
  + < MaxRetries > 1000 < / MaxRetries > +.
  + < CompressionLimit > 1000000 < / CompressionLimit > +.
  + < KeepAlive > 100000 < / KeepAlive > +.
  + < KeepAliveWait > 200000 < / KeepAliveWait > +.
  + < / SessionProfile > +.
  + < name of session = "session_1" > +.
  + JDOM < LocalAccessPointName > < / LocalAccessPointName > +.
  + TDOM < RemoteAccessPointName > < / RemoteAccessPointName > +.
  + < Nom_de_profil > profile_1 < / ProfileName > +.
  + < / session > +.
  + < / TuxedoConnector > +.
  
  standalone. XML
  
  ....
  + < subsystem xmlns = "urn: jboss:domain:resource - adapters: 1.1" > +.
  + < resource adapters > +.
  + < adapter resources - > +.
  + < archive > +.
  com.oracle.tuxedo.TuxedoAdapter.rar
  + < / archive > +.
  + < transaction-support > LocalTransaction < / transaction-support > +.
  + < connection-definitions > +.
  + < class-name = "com.oracle.tuxedo.adapter.spi.TuxedoManagedConnectionFactory" - name = jndi connection-definition "" java: / ist/TuxedoConnectionFactory "enabled ="true"use-java-context = 'false' pool-name =" java: jboss/ist/TuxedoConnectionFactory "/ > +"
  + < / connection-definitions > +.
  + < / adapter resources > +.
  + < / resource adapters > +.
  + < / subsystem > +.
  ...
  
  Dmconfig
  
  * DM_RESOURCES +.
  +#+
  VERSION = U22
  +#+
  * DM_LOCAL_DOMAINS +.
  +#+
  TDOM GWGRP = GRUPO3
  TYPE = TDOMAIN
  NETWORKID = "TDOM1."
  PERIOD = 60
  DMTLOGDEV = "/ appl/sf/tux/logs/DMTLOG.
  DMTLOGNAME = DMTLOG
  SECURITY = NONE
  +#+
  * DM_REMOTE_DOMAINS +.
  +#+
  TYPE = TDOMAIN JDOM
  NETWORKID = "JDOM1."
  +#+
  
  * DM_TDOMAIN +.
  +#+
  TDOM NWADDR = "//maqueta2:5000".
  JDOM NWADDR = "//maqueta2:5001".
  * DM_LOCAL_SERVICES +.
  TOUPPER
  
  
  It's the connection in ULOG:
  
  174335.maqueta2! GWTDOMAIN.26860.4.0: LIBGWT_CAT:1128: INFO: accepted connection of the field (networkid = < JDOM1 >)
  
  and the jboss:
  
  17:59:57, 618 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (service MSC 1-32 thread) IJ020002: deployed: file:/export/home/jboss/jboss-eap-6.1/standalone/tmp/vfs/tempd94ea707efb676cf/com.oracle.tuxedo.TuxedoAdapter.rar-f7058dab3d57d6b6/contents/
  17:59:57, 626 INFO [org.jboss.as.connector.deployment] (the MSC 1-55 service thread) JBAS010401: JCA ConnectionFactory enlazado [java: / ist/TuxedoConnectionFactory]
  17:59:57, 758 INFO [org.jboss.as.server] (HttpManagementService-NET - 1) JBAS018559: Implementado "com.oracle.tuxedo.TuxedoAdapter.rar" (name-DURATION: 'com.oracle.tuxedo.TuxedoAdapter.rar')
  17:59:58, 144 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180072 > < +++ / tplle/crypFinishOne/send_key (16) +++ >
  17:59:58, 147 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180113 > < 0 C F3 E2 49 51 93 2F A5 92 48 07 1 7F F4 92 A3... IQ? ?? H...??. >
  17:59:58, 149 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180073 > < +++ END +++ >
  17:59:58, 151 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180072 > < +++ / tplle/crypFinishOne/recv_key (16) +++ >
  17:59:58, 153 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180113 > < A5 DA EF 93 BE 79 E7 80 51 37 47 F5 77 C1 C0 AF? ?? y.? Q7G.w.. ? >
  17:59:58, 154 INFO [stdout] (by default-NET - 2) < kills Jun 04 17:59:58 CEST 2013 > < Debug > < WTC > < BEA-180073 > < +++ END +++ >
  17:59:58, 178 INFO [com.oracle.tuxedo.utils.TuxedoLogger] (by default-NET - 2) makes the connection to the remote domain TDOM1.
  
  
  
  But when I prove the service, the only thing I get is TPENOENT
  
  18:01:11, 888 ERROR [stderr] (http-/0.0.0.0:8080-1) TPENOENT (6): 0:0:TPED_MINVAL (0): QMNONE (0): 0:There no resources imported with name TOUPPER is configured!
  
  I don't know what else to do!
  
  Thanks in advance

  I solved the problem with the TPENOENT.

  All the configuration was ok, the problem came from libraries outside smoking. I put them in the package of the ear and not as global libraries in jboss (in the form of plug-ins).

  For some reason any if you don't resolve the dependencies of your servlet, ejb... of these libraries, you are out of the context of smoking.

• Producers set connection cache, Session, JMS

  I read a very interesting articles about caching of JMS
  
  https://community.JBoss.org/wiki/ShouldICacheJMSConnectionsAndJMSSessions
  http://bsnyderblog.blogspot.be/2010/02/using-spring-JmsTemplate-to-send-JMS.html
  
  It made me ask if I use JMS in a proper way for sending messages
  (for MDB is easy to specify the number of consumers and I guess only he connections are managed by the container and are advised)
  
  First scenario is s local search:
  
  When I want to send messages JMS to a stateless session bean:
  
  Context ctx = new world;
  Factory Factory = ctx.lookup("jms.apps.QueueConnectionFactory") (Factory);
  Connection Conn = queueConnectionFactory.createConnection ();
  Conn.Start ();
  A session = conn.createSession (false, Session.AUTO_ACKNOWLEDGE);
  Destination destination = ctx.lookup (queueName) (Destination);
  MessageProducer myMsgProducer = session.createProducer (destination);
  TextMessage m = session.createTextMessage (message);
  myMsgProducer.send (m);
  Conn.Close ();
  
  Is this ok?
  
  I want to say to every call there is this sequence == >
  
  -> Send-> connection-> Session-> MessageProducer ConnectionFactory
  
  You article he wrote (but is for JBOSS):
  
  "The reason is, when you use the JMS API from within an EJB (including an MDB), or a servlet (or an MBean in JBoss), and then when you call createConnection() or createSession() on your JMS connections or JMS connection factory, you do not actually those calls on a real JMS connections or JMS connection factory."
  
  Is this valid for Weblogic?
  
  Scenario 2: Using an InitialContext distance: is there a big penalty for remote access to this factory of conn (or is by default a cache, gives in fact)?
  
  Thank you

  Basically, the answer is Yes: a WebLogic application server will be "secretly" share the JMS resources. That said, it's a good idea for applications to cache CF and dest references as it is expensive to repeatedly look up in JNDI - local or remote JNDI context. (This is a common practice to use remote contexts, the links below detail best practices for their wiring in WebLogic). I think that it is also a good idea to refresh the references CF and dest on an error. In addition, in your code example, there is no need to call the "connection.start ()" - as it has no effect on message production.

  Here are the related documentation for WebLogic:

  Increased support for WebLogic JMS with EJB and servlet usage
  http://docs.Oracle.com/CD/E17904_01/Web.1111/e13727/J2EE.htm#g1329180
  There's a nice sample EJB 3.0 at the end of this chapter. I recommend to do two things a bit differently from the sample: (1) do not raise again the exception to trigger the return as this expensive forces bean to be destroyed and re-created, force rather a cancellation of transaction by using the context of the EJB - that said, new lifting is inevitable with non transactional BMD, because there is no equivalent to a cancellation in the case of no transaction request , and (2) the value targetDest and targetCF to null in the exception handler to be refreshed on an error.

  Integrate remote JMS providers
  http://download.Oracle.com/docs/CD/E17904_01/Web.1111/e13727/Interop.htm#JMSPG553

  Message-Driven Beans programming
  http://download.Oracle.com/docs/CD/E17904_01/Web.1111/e15493/TOC.htm

• Coordination of cache using jms password problem

  Hi all
  I used jms to cache coordination in EclipseLink. Things using an excellent clear text password until now work. However, when I use an encrypted password generated by going to the weblogic, setDomainEnv.sh execution and execution domain java weblogic.security.Encrypt. I get a {...} AES = password I use in the transport Manager by the definition of password in encrypted for the transport Manager. But I get authentication exception. Is there something that I am missing? For clear text, there seems to be no problems. Any help would be appreciated. I have attached the stacktrace for reference.
  
  Thank you
  Prashanth.
  
  StackTrace:
  
  Caused by: Exception [EclipseLink-22106] (Eclipse - 1.2.0.v20091016 persistence Services - r5565): org.eclipse.persistence.exceptions.RemoteCommandManagerException
  Description of the exception: could not create external JMS connection with the PomsTopic topic, topic factory PomsTopicConnectionFactory and context properties {java.naming.provider.url=t3://joust.us.oracle.com:7303, java.naming.factory.initial is weblogic.jndi.WLInitialContextFactory, java.naming.security.principal = weblogic, dedicated.connection = true, java.naming.security.credentials={AES}1mh2MR5XXPo4E9+tz8++ydo9Soxu/nQoWjpcV5HApOk=}
  Inner exception: Exception [EclipseLink-22101] (Eclipse - 1.2.0.v20091016 persistence Services - r5565): org.eclipse.persistence.exceptions.RemoteCommandManagerException
  Description of the exception: could not get JNDI context with properties {java.naming.provider.url=t3://joust.us.oracle.com:7303, java.naming.factory.initial is weblogic.jndi.WLInitialContextFactory, java.naming.security.principal = weblogic, dedicated.connection = true, java.naming.security.credentials={AES}1mh2MR5XXPo4E9+tz8++ydo9Soxu/nQoWjpcV5HApOk=}
  Inner exception: javax.naming.AuthenticationException [root exception is javax.security.auth.login.FailedLoginException: [Security: 090304] authentication failed: user weblogic javax.security.auth.login.FailedLoginException: [Security: 090302] authentication failed: user weblogic denied]
  at org.eclipse.persistence.exceptions.RemoteCommandManagerException.errorCreatingJMSConnection(RemoteCommandManagerException.java:129)
  at org.eclipse.persistence.sessions.coordination.jms.JMSTopicTransportManager.createConnection(JMSTopicTransportManager.java:107)
  at org.eclipse.persistence.sessions.coordination.jms.JMSTopicTransportManager.createExternalConnection(JMSTopicTransportManager.java:59)
  at org.eclipse.persistence.sessions.coordination.jms.JMSTopicTransportManager.createConnections(JMSTopicTransportManager.java:146)
  at org.eclipse.persistence.sessions.coordination.RemoteCommandManager.initialize(RemoteCommandManager.java:148)
  at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.postConnectDatasource(DatabaseSessionImpl.java:674)
  at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login(DatabaseSessionImpl.java:633)
  at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:205)
  at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:186)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)
  at weblogic.deployment.EntityManagerFactoryProxyImpl.invoke(EntityManagerFactoryProxyImpl.java:75)
  to $Proxy142.createEntityManager (Unknown Source)
  at weblogic.deployment.TransactionalEntityManagerProxyImpl.newPersistenceContext(TransactionalEntityManagerProxyImpl.java:75)
  at weblogic.deployment.BasePersistenceContextProxyImpl.getPersistenceContext(BasePersistenceContextProxyImpl.java:160)
  at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:88)
  at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:91)
  at weblogic.deployment.BasePersistenceContextProxyImpl.invoke(BasePersistenceContextProxyImpl.java:80)
  at weblogic.deployment.TransactionalEntityManagerProxyImpl.invoke(TransactionalEntityManagerProxyImpl.java:26)
  to $Proxy181.hashCode (Unknown Source)
  at java.util.HashMap.put(HashMap.java:372)
  at java.util.HashSet.add(HashSet.java:200)
  at oracle.communications.platform.persistence.impl.PersistentBaseImpl.getPersistenceManager(PersistentBaseImpl.java:243)
  at oracle.communications.platform.persistence.impl.FinderBean.findByJPQL(FinderBean.java:629)
  at oracle.communications.integrity.management.ResourceProviderMXBeanImpl.init(ResourceProviderMXBeanImpl.java:87)
  at oracle.communications.integrity.management.ResourceProviderMXBeanImpl.preRegister(ResourceProviderMXBeanImpl.java:79)
  at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegisterInvoke(DefaultMBeanServerInterceptor.java:1010)
  at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:938)
  at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
  at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
  at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
  to weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$ 27.run(WLSMBeanServerInterceptorBase.java:714)
  at java.security.AccessController.doPrivileged (Native Method)
  at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.registerMBean(WLSMBeanServerInterceptorBase.java:709)
  at weblogic.management.mbeanservers.internal.JMXContextInterceptor.registerMBean(JMXContextInterceptor.java:448)
  to weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$ 27.run(WLSMBeanServerInterceptorBase.java:712)
  at java.security.AccessController.doPrivileged (Native Method)
  at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.registerMBean(WLSMBeanServerInterceptorBase.java:709)
  at weblogic.management.jmx.mbeanserver.WLSMBeanServer.registerMBean(WLSMBeanServer.java:444)
  at oracle.communications.integrity.management.WebApplicationLifeCycleCallBack.contextInitialized(WebApplicationLifeCycleCallBack.java:52)
  to weblogic.servlet.internal.EventsManager$ FireContextListenerAction.run (EventsManager.java:481)
  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
  at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
  at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
  at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1801)
  at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
  at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
  at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
  to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
  at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
  at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
  at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
  to weblogic.application.internal.flow.ModuleStateDriver$ 3.next(ModuleStateDriver.java:425)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
  at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
  at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
  to weblogic.application.internal.BaseDeployment$ 2.next(BaseDeployment.java:1267)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
  at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
  at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
  at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
  at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
  at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
  to weblogic.management.deploy.internal.DeploymentAdapter$ 1.doActivate(DeploymentAdapter.java:51)
  at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
  to weblogic.management.deploy.internal.AppTransition$ 2.transitionApp(AppTransition.java:30)
  at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
  at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
  at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
  at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
  at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

  TransportManager has a setEncryptionClassName (String) which allows the specification of the securable class strategy that it will use that can also be set throgh the encryption tag xml class if you use EclipseLink installation sessions.xml/project.xml native config files. Otherwise, you will probably need to call the setEncryptionClassName directly from within a method of session customizer: session.getCommandManager () .getTransportManager () .setEncryptionClassName ("yourclass"); start the session CommandManager or AbstractSession

  Best regards
  Chris

• Error with remote JMS

  Hello...
  
  I try to create a simple application that sends a message to the JMS Weblogic Server. This works if the application deployed on the same server with my JMS weblogic. But if I put the JMS server in another weblogic server, I get this error:

  java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
       at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
       at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
       at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
       at weblogic.jms.frontend.FEConnectionFactoryImpl_1030_WLStub.connectionCreateRequest(Unknown Source)
       at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:224)
       Truncated. see log file for complete stacktrace

  I already have user domain (as a result of the documentation), or use of overall confidence. But none of them can work. Have you guys any reference or can give me step by step, deploying this JMS distance?
  
  BTW, I use the spring to my client with configuration jndi as follows

       <bean id="jndiTemplate"
            class="org.springframework.jndi.JndiTemplate">
            <property name="environment">
                 <props>
                      <prop key="java.naming.factory.initial">
                           weblogic.jndi.WLInitialContextFactory
                      </prop>
                      <prop key="java.naming.provider.url">
                           t3://otherserver:7001
                      </prop>
                      <prop key="java.naming.security.authentication">simple</prop>
                      <prop key="java.naming.security.principal">weblogic</prop>
                      <prop key="java.naming.security.credentials">weblogic</prop>                     
                 </props>
            </property>
       </bean>

  THX.
  André

  Hello

  "connection could not be found" exceptions are often a symptom of a bad configuration where there are duplicate names defined in two different areas. In WebLogic, you must:

  -Ensure that each area has a different name.

  -Each WL server has a different name (even if they are in different domains)

  -Each JMS server has a different name (even if they are in different domains - probably not necessary in your case, but it is good to play it safe)

  If you post some time in the future, please always try to include the record of the full stack of the journal - not only the truncated version.

  Tom

• Phone verification (two-factor authentication) on Sierra is not available in Bangladesh

  I upgraded to El Capitan in macOS Sierra today. But when I tried to set up two mobile verification or authentication my country (Bangladesh) was not listed there. I was wondering why this service is not available here in Bangladesh? Please give me a solution for telephone based it services.

  If it is not supported in your country, then I'm afraid you're out of luck. As to why, you have to ask Apple https://getsupport.apple.com/ instead we support single users in these Community Forums.

• Two-factor authentication

  On my iMac after Sierra was an option to unlock with Apple Watch (security preferences panel). I click it and it says I need to disable the verification of two factor and enable two-factor authentication. Fine.

  Did. Now the option to activate Apple Watch unlock on the mac has disappeared.

  It works on my other Mac but not the iMac.

  Also in the preferences to iCloud account, then on devices, I see that my Apple Watch can be used to receive the codes!

  Someone knows how to fix these?

  Tried to run iCloud power switch, disconnect the watch and repair, restart everything.

  

  Just to be clear, the Mac is capable of auto unlock, it's an iMac end of 2015 and system report confirms it is compatible.

  The apple support page also suggests watches should be able to receive the codes:

  

• Can I choose my device of trust preferred to iCloud two-factor authentication?

  I've recently implemented Icloud two-factor authentication, because I love the he adds extra security.

  As usual, I have my macbook on me, I also have to log on windows pc, every now and then.

  Unfortunately, ICloud chooses my headless mac mini which I use as a server at home instead of my laptop or Iphone.

  I would like to stop receiving the confirmation on this machine code, everyone was faced with a similar problem?

  If so how to solve it?

  Codes to go to all the secure devices.

  

  Of course, you can trust features remove at any time.

  

• When you try to configure the authentication of two step my location appears as a bad place

  Hi, I'm trying to implement the authentication of two floors on all my devices, however when I do this I get a message on another device connected in iCloud saying that another device is trying to connect in icloud to a display location near London, I don't live in London but.

  Could someone help?

  I'm having the same problem! Having the two devices in front of me, but have the message saying that another device tries to log on to London? I also don't live anywhere near London, I recently updated my email ID well and it's the old e-mail ID that requires authentication?

  Sorry I can not help but hoping someone else has an answer us?