Context Propagation - Bug Weblogic 81 SP1

Im trying to create a new InitialContext based on a principal and credential(non-admin)
and locate some resources from the initial context.
My issue is after the initial context is retrieved, weblogic should be using the
standard account(the principal that it was using before obtaining the initial
context) to do the rest of the work. I am observing that this is NOT the case
and it continues to use the principal i specified to do the rest of the operations.
For e.g. i get a
Access not Allowed for subject:principals=[operator, Operators], on ResourceType:
DomainLogHandlerRuntime Action: execute Target: registerToMe.
which i suppose should have been called using an admin account.
This is explicitly visible in my case where my class is a startup class and weblogic
doesnt complete its initializing until the startup classes are loaded. Please
let me know if this is a bug.
Thanks
Raj

Similar Messages

Bug or design in Weblogic 6 SP1?

In Weblogic 6 SP1 console, the DEFAULT web application cannot be
redeployed by unchecking and checking the "deployed" box. The
result is, if I update any code in my application, or I have to
rely on the automatica redelpoy work, or restart the server. The
problem is definitely not from the application setup since it
works smoothly without Service Pack1 and it also works as non-
default Web application, for example, when I just make a copy of
the same application and set it as non-default. It is really a
frustrating new feature if it is a new design.
Also when the console is set as default Web application, the
left pane applet will not appear and socket errors are expected
somewhere.

Jay Fowler wrote:
Is this a bug or a feature?I wouldn't call this a bug (defined as "does not work as designed"). I
would call this an unfortunate effect of the different Admin CGIs/JSPs.
The CGI/JSP that creates the normal redirects is apparantly not checking
for the existence of User Home Dirs and placing its redirects above them
in the obj.conf. You can define all you redirects via the Admin
interface, then manually move the
NameTrans fn="unix-home" from="/~" subdir="public_html"
line under the redirects you created. You'll have to do this any time
you define a redirect that is based off of "/~foo".
JMcCabe People will accept your ideas much more
Moz' Whelp readily if you tell them that Benjamin
Franklin said it first.

Security info propagation across weblogic servers

Hi,
I have a requirement wherein my biz layer needs info abt logged in user profile. the web layer authenticates user using weblogic internal ldap and calls session bean of biz layer. In the biz layer i m able to retrieve the loggedin userid using sessionContext.getCallerPrincipal(). But i do need more info like user_preferences,emp_id as well. Is there a way of setting these attributes in Context obj which gets propagated across weblogic servers transparently. Otherwise i need to modify all my session bean api to accept userPreferencesDTO as additional parameter.
Please advise,
venkat

have you find any solution for this...

Problem with Weblogic Builder SP1

I have a problem with Weblogic Builder SP1. I basically re-used my EJB deployment
descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loading my EJB
in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
I re-attempted by jarring my EJB with WL5.1 descriptors and used my friend's WB
(not SP1) to export new descriptors which I used to re-jar. This new EJB is again
not recognised by WB SP1?
What is wrong?

The exception is as follows:
Opening module myproj.jar
java.lang.NullPointerException
     at java.util.Arrays.sort(Arrays.java:1181)
     at weblogic.marathon.model.EJBJarCMBean.initRelations(EJBJarCMBean.java:1212)
     at weblogic.marathon.model.EJBJarCMBean.initBeans(EJBJarCMBean.java:1098)
     at weblogic.marathon.model.EJBJarCMBean.setup(EJBJarCMBean.java:1144)
     at weblogic.marathon.tasks.OpenModuleTask.getEJBModule(OpenModuleTask.java:156)
     at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:191)
     at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:230)
     at weblogic.marathon.tasks.OpenModuleTask.runBackground(OpenModuleTask.java:89)
     at weblogic.tools.jellybeans.core.task.TaskThread.execute(TaskThread.java:127)
     at weblogic.tools.jellybeans.core.task.TaskThread.run(TaskThread.java:64)
Module myproj.jar descriptors failed to load
The EJB has no problem deploying.
Rob Woollen <[email protected]> wrote:
You'll have to at least show us the error you get from marathon.
Does your application deploy to the server?
-- Rob
Robin Tan wrote:
I have a problem with Weblogic Builder SP1. I basically re-used myEJB deployment
descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loadingmy EJB
in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
I re-attempted by jarring my EJB with WL5.1 descriptors and used myfriend's WB
(not SP1) to export new descriptors which I used to re-jar. This newEJB is again
not recognised by WB SP1?
What is wrong?

Bug (LabVIEW 2011 sp1 crash)

Bug (LabVIEW 2011 sp1 crash)
1) Open LabVIEW
2) Blank VI
3) Front Panel / View / Class Browser
follow exactly this :
Class Browser / Object library ---> select "LabVIEW Classes" ---> and then clic "Search"
result : The window "Class Browser Search" opens ----> do nothing ... just "Cancel"
back to the window Class Browser ...
Class Browser / Object library ----> now select "DAQmx"
result : in the window Class Browser : Objet library = DAQmx
Class = DAQmx buffer
don't touch anything else (!)
and now clic "Search" ... LV CRASH

When you meet your colleagues, could you ask them, of course when they have time, to create this number.
This will make me happy, and this would be a small reward for this bug report.
Thank you very much in advance ThiCop

Help me! Change Context root in weblogic portal 10.3.2

I has a desktop in weblogic portal with path is: http://localhost:7001/ABC/appmanager/t1/home , I want to change the string ABC => Portal with new is the path: http://localhost:7001/Portal/appmanager/ v1/home How to configuration? I need config file? .The users help to resolve the problem this
Thanks you very much! Hoping to replay soon!!!

Thanks Sanjeev Kumar has replay topic!
I have followed your instructions by: replace <display-name>Portal</display-name> in web.xml and <wls:context-root>Portal</wls:context-root> in weblogic.xml , then I redeploy up server portal weblogic then runing path new is http://localhost:7001/Portal/appmanager/t1/home , throw error:
Resource /t1/home could not be resolved for locale null. I think problem related to database when I create desktop. I view database see context root ABC resource in PF_Desktop_instance and PF_Desktop_Defination.How to update name colum WebApp in two table?
Thanks you very much! Hoping to replay soon!!!
Edited by: 890028 on Feb 15, 2012 11:12 PM

[svn:fx-trunk] 9215: Event Propagation bug fix

Revision: 9215
Author:   [email protected]
Date:     2009-08-10 17:30:21 -0700 (Mon, 10 Aug 2009)
Log Message:
Event Propagation bug fix
http://bugs.adobe.com/jira/browse/SDK-21044 - Spark Components should use event.preventDefault instead of event.stopPropagation
Since keyboard are now cancellable, the Spark components should use event.preventDefault() / event.isDefaultPrevented() instead of event.stopPropagation. I updated ButtonBar, RadioButton, and DropDownList to use preventDefault(). Also cleaned up Slider and Spinner to always assume the event is cancellable.
QE notes: Add tests with these components inside of scrollable containers
Doc notes: None
Bugs: SDK-21044
Reviewer: Hans
Tests run: Slider, Spinner, RadioButton, ButtonBar, DropDownList
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21044
    http://bugs.adobe.com/jira/browse/SDK-21044
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/ButtonBar.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RadioButton.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Spinner.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/DropDownCont roller.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

error dateField not selecion date 27/11/2002 ?
This is bug flex 3 ?
thanks

Transaction Context Propagation

Can transaction context be propagated from one WebLogic Server to another? If yes, what is then the relationship between the two Transaction Managers in each server?


Zhenxin,
          Transaction can be propagated between multiple instances of the server.
          In releases 5.1 and below, all databse access in this case was delegated to 1 jdbc connection in 1 pool on 1 server, and the database transaction manager was used.
          In 6.0 and above, the transaction is co-ordinated by the TM in one instance of the server, which calls on the remote instances during the pre-commit and commit phases.
          I believe that currently the 1st server to be invoked in the transaction is the one who gets the commit responsibility, but this is an implementation detail that may
          change in future.
          I hope that helps.
          Regards,
          Peter.
          Got a Question? Ask BEA at http://askbea.bea.com
          The views expressed in this posting are solely those of the author, and BEA
          Systems, Inc. does not endorse any of these views.
          BEA Systems, Inc. is not responsible for the accuracy or completeness of the
          information provided
          and assumes no duty to correct, expand upon, delete or update any of the
          information contained in this posting.
          Zhenxin Wang wrote:
          > Can transaction context be propagated from one WebLogic Server to another? If yes, what is then the relationship between the two Transaction Managers in each server?

Caller id propagation from WebLogic Express to WebLogic Server

Hi all,
I'm planning on a WebLogic configuration where Servlets executing in
WebLogic Express invoke EJBs executing in WebLogic Server. The Web container
and the EJB container are thus executing in different processes.
Given that a user is authenticated in WebLogic Express using e.g. the
J2EE-standard form-based authentication, would the user id be propagated to
the EJB container automatically?
Thanks
Patrik Gottfridsson
Valtech

Call flow was :
CUCM---Router-----MPLS----Router---CME
extension 1040 from cucm was calling extension 2800 on CME, and on the display from the phone that is registered on CME had the "UNKNOWN" on it.
But I just figured it out.
Thanks anyways!

Undo Sheet Deletion Bug (DIAdem 2014 SP1)

Hello,
I am experiencing a bug in the Report section of DIAdem.
I have ~80 sheets in a report. I delete the last one by right clicking and selecting "Delete". I confirm the deletion when prompted and the sheet goes away. I now press Ctrl-Z to undo the deletion. DIAdem appears to reload the whole set of 80 sheets and the sheet that I deleted is back. The undo function works.
The problem I have now is that I lose the mouse input for the report section and data portal. I am able to change the view to NAVIGATOR, VIEW, etc. with the mouse but I can't click on anything else including the pull-down menus. Keyboard navigation works as I can move around the report and edit Text blocks, etc. but the mouse input is completely gone.
I am using DIAdem 2014 SP1. Can anyone replicate this issue?
Thanks,
Jacob

Hi Jacob,
Could you export your DIAdem reports as a .TDR file so we can try it out on another system and see if the problem is reproducable?
Thanks

Help with Weblogic 6 sp1 Custom Realm !!!!

We are trying to run Weblogic 6.0 sp1 with our current environment (ejb 1.1, custom
security realm)
We can compile and deploy our ejb 1.1 beans. We wish to start with ejb1.1 and
move to ejb2.0 once we can get our custom security working.
The JDBC connection pools are fine.
Our custom security realm uses LDAP for user authentication and an Oracle table
for authorization (acls).
Earlier, I wrote to the board and received the below following instructions to
use our existing custom realm in wl 60. You can read below, but I followed these
instructions on Solaris 5.6.
1. I ensured the SunOS patches were up to date.
2. We ensured the LD_LIBRARY_PATH reflected weblogic 6 (and not 5.1). We moved
the 5.1 classes over to wl6.
3. We copied our custom realm properties file to the weblogic root and/or the
config subdirectory (tried them both).
4. We ensured the security realm class we wrote is in the classpath (we bunch
all our serverside classes in a jar file anyway).
5. Then we created a custom realm via the console – name BFXRealm and it’s
class name <package>.BFXRealm, left configuration box blank.
6. Then we created a custom caching realm BFXCachingREalm and set its basic realm
as the custom realm, BFXRealm. All of the enable caches are checked to true.
7. Then we set the default realm to the BFXCachingRealm.
Now, when we perform a query, the everyone group should be implied. We don’t
implement LDAP lookup on queries. If I try to run a query from a client, I see
the client box connecting with the server:
Last line - you can see the client box connecting to the server -
<May 30, 2001 2:20:07 PM EDT> <Info> <J2EE> <Deployed : DefaultWebApp_myserver>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <WebLogic Server started>
<May 30, 2001 2:20:07 PM EDT> <Info> <Configuration Management> <Backed up booted
configuration /opt/apps/weblogic/beasp1/wlserver6.0sp1/./config/mydomain/config.xml
at /opt/apps/weblogic/beasp1/wlserver6.0sp1/./config/mydomain/config.xml.booted>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <SSLListenThread listening
on port 7002>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <System has file
descriptor limits of - soft: '1024', hard: '1024'>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <Using effective
file descriptor limit of: '1024' open sockets/files.>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <Allocating: '3'
POSIX reader threads>
<May 30, 2001 2:20:23 PM EDT> <Info> <HTTP> <[HTTP myserver] Created log stream
/opt/apps/weblogic/beasp1/wlserver6.0sp1/config/mydomain/logs/access.log>
<May 30, 2001 2:21:50 PM EDT> <Info> <WebLogicServer> <Adding address: 152.51.164.233/152.51
The client receives the error:
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
Authentication
for user aws4270 denied in realm weblogic
It’s as if the fileRealm.properties is only being looked at. We do not
use this for our user/groups/acls in wl5.1.0 and we do not want to in wl6
For “fun”, I added a user to the fileRealm.properties file via the
console and ran a client query. It worked.
But when I tried to call an ejbCreate from the client, I received these errors
from the server:
BFXSecurityRealmException is a custom exception we have written. A query works
but a create does not - obviously cannot get to acl in database (?)
and why the ejb20 errors? We just want to start with ejb 1.1
In SeqStoreSecurityHelper.isUserAuthorized(): schema = seqStore.INTNUC, class
= bioseq, project = HIPPI, permission = create
<May 30, 2001 2:50:10 PM EDT> <Info> <EJB> <EJB Exception in method: ejbCreate:
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBean.ejbCreate(BioSequenceBean.java:1562)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanImpl.ejbCreate(BioSequenceBeanImpl.java:833)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.DBManager.create(DBManager.java:408)
at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:353)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanHomeImpl.create(BioSequenceBeanHomeImpl.java:111)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanHomeImpl_WLSkel.invoke(BioSequenceBeanHomeImpl_WLSkel.java:78)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
The client receives the error:
java.rmi.RemoteException: EJB Exception:; nested exception is:
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
o
ccurred.
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
HOW CAN WE GET THE SERVER TO BYPASS FILEREALM and use BFXREALM ???????????
Thanks,
Anne
Subject: Re: Do Custom Security Realms have to use Mbeans?
Date: 17 May 2001 06:38:23 -0800
From: "Tom Moreau" <[email protected]>
Newsgroup: weblogic.developer.interest.security
Yes this can be done. Here's how:
1) I'll assume that the classname to your custom realm is "com.yourcompany.YourCustomRealm"
2) I'll assume that your custom realm has some kind of properties file from which
it reads its configuration data. Let's call this file "YourCustomRealm.properties"
3) Copy YourCustomRealm.properties to every machine that you're running wls on
(you are probably already doing this today).
4) Make sure that com.yourcompany.YourCustomRealm is in the classpath when you
start wls (you should already be doing this today)
5) In 5.1, there used to be some utility classes that customers used for their
custom realms - something about Pools & Factories. These have been renamed in
6.0. If you're using these classes, then go to your 5.1 weblogic jar file and
pull out these classes and add them to your classpath for 6.0.
6) In the console, create a custom realm and set it's realm class name to com.yourcompany.YourCustomRealm.
Leave the configuration data section blank.
7) In the console, configure your custom realm as the alternate realm. That is,
create a caching realm and set it's basic realm to your custom realm, then set
the realm's caching realm to the caching realm you just created.
I'm pretty sure this should work for you. We did this to provide a patch that
let 6.0 users uses the LDAPRealm rewrite from 5.1.
The downside is that you don't get single point of administration - that is, you
have to make your custom realm's configuration data (YourCustomRealm.properties)
available on all the machines you're running WLS on. If you rework your custom
realm, then the configuration data gets put in the custom realm configuration
you create via the console and automatically copied to other machines for you.
- Tom

We are trying to run Weblogic 6.0 sp1 with our current environment (ejb 1.1, custom
security realm)
We can compile and deploy our ejb 1.1 beans. We wish to start with ejb1.1 and
move to ejb2.0 once we can get our custom security working.
The JDBC connection pools are fine.
Our custom security realm uses LDAP for user authentication and an Oracle table
for authorization (acls).
Earlier, I wrote to the board and received the below following instructions to
use our existing custom realm in wl 60. You can read below, but I followed these
instructions on Solaris 5.6.
1. I ensured the SunOS patches were up to date.
2. We ensured the LD_LIBRARY_PATH reflected weblogic 6 (and not 5.1). We moved
the 5.1 classes over to wl6.
3. We copied our custom realm properties file to the weblogic root and/or the
config subdirectory (tried them both).
4. We ensured the security realm class we wrote is in the classpath (we bunch
all our serverside classes in a jar file anyway).
5. Then we created a custom realm via the console – name BFXRealm and it’s
class name <package>.BFXRealm, left configuration box blank.
6. Then we created a custom caching realm BFXCachingREalm and set its basic realm
as the custom realm, BFXRealm. All of the enable caches are checked to true.
7. Then we set the default realm to the BFXCachingRealm.
Now, when we perform a query, the everyone group should be implied. We don’t
implement LDAP lookup on queries. If I try to run a query from a client, I see
the client box connecting with the server:
Last line - you can see the client box connecting to the server -
<May 30, 2001 2:20:07 PM EDT> <Info> <J2EE> <Deployed : DefaultWebApp_myserver>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <WebLogic Server started>
<May 30, 2001 2:20:07 PM EDT> <Info> <Configuration Management> <Backed up booted
configuration /opt/apps/weblogic/beasp1/wlserver6.0sp1/./config/mydomain/config.xml
at /opt/apps/weblogic/beasp1/wlserver6.0sp1/./config/mydomain/config.xml.booted>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<May 30, 2001 2:20:07 PM EDT> <Notice> <WebLogicServer> <SSLListenThread listening
on port 7002>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <System has file
descriptor limits of - soft: '1024', hard: '1024'>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <Using effective
file descriptor limit of: '1024' open sockets/files.>
<May 30, 2001 2:20:08 PM EDT> <Info> <Posix Performance Pack> <Allocating: '3'
POSIX reader threads>
<May 30, 2001 2:20:23 PM EDT> <Info> <HTTP> <[HTTP myserver] Created log stream
/opt/apps/weblogic/beasp1/wlserver6.0sp1/config/mydomain/logs/access.log>
<May 30, 2001 2:21:50 PM EDT> <Info> <WebLogicServer> <Adding address: 152.51.164.233/152.51
The client receives the error:
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
Authentication
for user aws4270 denied in realm weblogic
It’s as if the fileRealm.properties is only being looked at. We do not
use this for our user/groups/acls in wl5.1.0 and we do not want to in wl6
For “fun”, I added a user to the fileRealm.properties file via the
console and ran a client query. It worked.
But when I tried to call an ejbCreate from the client, I received these errors
from the server:
BFXSecurityRealmException is a custom exception we have written. A query works
but a create does not - obviously cannot get to acl in database (?)
and why the ejb20 errors? We just want to start with ejb 1.1
In SeqStoreSecurityHelper.isUserAuthorized(): schema = seqStore.INTNUC, class
= bioseq, project = HIPPI, permission = create
<May 30, 2001 2:50:10 PM EDT> <Info> <EJB> <EJB Exception in method: ejbCreate:
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBean.ejbCreate(BioSequenceBean.java:1562)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanImpl.ejbCreate(BioSequenceBeanImpl.java:833)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.DBManager.create(DBManager.java:408)
at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:353)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanHomeImpl.create(BioSequenceBeanHomeImpl.java:111)
at com.gw.bioinfo.ejb.bioSeq.BioSequenceBeanHomeImpl_WLSkel.invoke(BioSequenceBeanHomeImpl_WLSkel.java:78)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
The client receives the error:
java.rmi.RemoteException: EJB Exception:; nested exception is:
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
o
ccurred.
com.gw.bioinfo.exception.BFXSecurityRealmException: BFX-90000: A BFXSecurityRealmException
occurred.
HOW CAN WE GET THE SERVER TO BYPASS FILEREALM and use BFXREALM ???????????
Thanks,
Anne
Subject: Re: Do Custom Security Realms have to use Mbeans?
Date: 17 May 2001 06:38:23 -0800
From: "Tom Moreau" <[email protected]>
Newsgroup: weblogic.developer.interest.security
Yes this can be done. Here's how:
1) I'll assume that the classname to your custom realm is "com.yourcompany.YourCustomRealm"
2) I'll assume that your custom realm has some kind of properties file from which
it reads its configuration data. Let's call this file "YourCustomRealm.properties"
3) Copy YourCustomRealm.properties to every machine that you're running wls on
(you are probably already doing this today).
4) Make sure that com.yourcompany.YourCustomRealm is in the classpath when you
start wls (you should already be doing this today)
5) In 5.1, there used to be some utility classes that customers used for their
custom realms - something about Pools & Factories. These have been renamed in
6.0. If you're using these classes, then go to your 5.1 weblogic jar file and
pull out these classes and add them to your classpath for 6.0.
6) In the console, create a custom realm and set it's realm class name to com.yourcompany.YourCustomRealm.
Leave the configuration data section blank.
7) In the console, configure your custom realm as the alternate realm. That is,
create a caching realm and set it's basic realm to your custom realm, then set
the realm's caching realm to the caching realm you just created.
I'm pretty sure this should work for you. We did this to provide a patch that
let 6.0 users uses the LDAPRealm rewrite from 5.1.
The downside is that you don't get single point of administration - that is, you
have to make your custom realm's configuration data (YourCustomRealm.properties)
available on all the machines you're running WLS on. If you rework your custom
realm, then the configuration data gets put in the custom realm configuration
you create via the console and automatically copied to other machines for you.
- Tom

MAJOR BUG WebLogic 4.5.1 and wl-proxy for Netscape server

Hi there. We are having a major problem with our WebLogic cluster that
          cannot be explained, but is bad enough where we can't deploy our
          application and miss our schedule. Here's the setup:
          We have 8 WebLogic servers (4.5.1) running on 2 Sun 5500 servers with
          2GB of RAM each running Solaris 2.6. The web server in front of the
          cluster is Netscape Enterprise Server version 3.6.2. We are using
          SunSoft's 1.1.7_07 (native threads) as our JDK to start the WebLogic
          servers. We are using in-memory replication on this cluster.
          Here's the problem. The first time we start up the cluster and the
          netscape server, things work fine for a while. It seems that everything
          works fine for the first 10 minutes. But then things start to slow
          down and response time grows exponentially until the browser start
          timing out and nothing works. When this happens, I can ping the servers
          directly and they all claim to be up. I can use the WebLogic console
          utility to connect to the cluster and see all 8 servers just sitting
          there, but I cannot access them through the wl-proxy on the netscape
          server. In fact, I can connect directly to one of the servers at port
          7001 with my browser and everything works fine...
          All of this had led me to believe the there is a serious bug in the
          wl-proxy (libproxy.so) for Solaris. The logs do not seem to indicate
          any problems, but this problem happens every time and we are running out
          of options. We have a WebLogic consultant on site, but he has not been
          able to shed any light on this issue.
          Anyone else experience something like this?? thanks in advance.
          --Vinny


Hi Prasad.. We do have a support issue open on this. I'll email you directly with the
          case#. We also have a WebLogic consultant onsite working with us, but we're just not
          getting anywhere with this issue and we're mere days away from deployment.. I was just
          hoping someone else in the newsgroups was also facing this same issue. We can recreate it
          every time we start our servers.
          Thanks
          --Vinny
          Prasad Peddada wrote:
          > Vinny,
          >
          > I am filing an issue about this. I would also suggest you call support to follow up
          > on this.
          > 1-888-232-7878 is the support number or [email protected]. I will try my best to
          > also keep track of this.
          >
          > Thanks
          > Prasad
          >
          > Vinny Carpenter wrote:
          >
          > > Hi Prasad.. Unfortunately that is not going to be acceptable. Our deployment date
          > > is November 1 and if we don't get this issue resolved by Thursday, we cannot go
          > > live.
          > >
          > > --Vinny
          > >
          > > Prasad Peddada wrote:
          > >
          > > > Vinny,
          > > > I can get to this but it won't be until next week. I have to install NES on
          > > > solaris box. I hope that's ok. If I get a chance I will try to test it before
          > > > that.
          > > >
          > > > Thanks
          > > > Prasad
          > > >
          > > > Vinny Carpenter wrote:
          > > >
          > > > > Hi Prasad.. We're a big Solaris/Sun shop and so it's going to be difficult to
          > > > > get a NT server and install NES. I can certainly try, but I am not sure we're
          > > > > going to be able to do that.
          > > > >
          > > > > Any other information I can provide?? Thanks
          > > > >
          > > > > --Vinny
          > > > >
          > > > > Prasad Peddada wrote:
          > > > >
          > > > > > Vinny,
          > > > > >
          > > > > > I don't know if you can do this but to further isolate the problem,
          > > > > > would it be possible to try with NES on NT and see if you still have the
          > > > > > problem.
          > > > > >
          > > > > > Thanks
          > > > > > Prasad
          > > > > >
          > > > > > Vinny Carpenter wrote:
          > > > > >
          > > > > > > Hi there. We are having a major problem with our WebLogic cluster that
          > > > > > > cannot be explained, but is bad enough where we can't deploy our
          > > > > > > application and miss our schedule. Here's the setup:
          > > > > > >
          > > > > > > We have 8 WebLogic servers (4.5.1) running on 2 Sun 5500 servers with
          > > > > > > 2GB of RAM each running Solaris 2.6. The web server in front of the
          > > > > > > cluster is Netscape Enterprise Server version 3.6.2. We are using
          > > > > > > SunSoft's 1.1.7_07 (native threads) as our JDK to start the WebLogic
          > > > > > > servers. We are using in-memory replication on this cluster.
          > > > > > >
          > > > > > > Here's the problem. The first time we start up the cluster and the
          > > > > > > netscape server, things work fine for a while. It seems that everything
          > > > > > > works fine for the first 10 minutes. But then things start to slow
          > > > > > > down and response time grows exponentially until the browser start
          > > > > > > timing out and nothing works. When this happens, I can ping the servers
          > > > > > > directly and they all claim to be up. I can use the WebLogic console
          > > > > > > utility to connect to the cluster and see all 8 servers just sitting
          > > > > > > there, but I cannot access them through the wl-proxy on the netscape
          > > > > > > server. In fact, I can connect directly to one of the servers at port
          > > > > > > 7001 with my browser and everything works fine...
          > > > > > >
          > > > > > > All of this had led me to believe the there is a serious bug in the
          > > > > > > wl-proxy (libproxy.so) for Solaris. The logs do not seem to indicate
          > > > > > > any problems, but this problem happens every time and we are running out
          > > > > > > of options. We have a WebLogic consultant on site, but he has not been
          > > > > > > able to shed any light on this issue.
          > > > > > >
          > > > > > > Anyone else experience something like this?? thanks in advance.
          > > > > > >
          > > > > > > --Vinny

Security Context Propagation between Managed Servers

          I'm using WLS 8.1 SP2. I have one domain, two managed servers, each on a separate
          hardware server. Each managed server hosts a different web application. I want
          to authenticate to Web App "A" and be able to invoke Web App "B" (from "A") without
          having to re-authenticate. Is this possible via configuration and, if so, how?
          Thanks.


Frank,
You do not have to do anything to propagate identity between the two
containers. As long as the user is authenticating first..
There have been a number of issues with the propagation, so be sure to stay up
on the service packs.
HTH.
Frank wrote:
How do you propagate security context information from Servlet to
EJBs? I have an web app that uses the container's FORM based authentication.
The servlet resource then calls a session EJB (w/ security contraints
setup). The webapp and the ejbs are bundled into one EAR.
Thanks!--
Tom Mitchell
[email protected]
Very Current Stoneham, MA Weather
http://www.tom.org

Transactional Context Propagation

Hi,
          Suppose that I a statefull session bean that uses a helper class to delegate
          its business methods. If the transactions are demarcated from the container
          will the transactional context of the caller (of the helper class) method be
          propagated to the helper class?
          Thank you in advance


          Hi,
          Is this true also for BMT? I have a problem where the UserTransaction
          object seems not to propagate from one BMT bean to another BMT bean.
          At least the status of the transaction
          (as retrieved by this.sessionContext.getUserTransaction().getStatus())
          is Status.STATUS_NO_TRANSACTION when checked in the method of th called bean.
          regards - Johan
          "Cameron Purdy" <[email protected]> wrote:
          >The transaction is bound to the thread, so yes, under most ordinary
          >conditions, the context would also apply to (or more likely through)
          >methods
          >of other classes called. Example: EJB A calls helper class method HC.foo()
          >calls HC.foo2() calls EJB B. If EJB A were in a transaction, EJB B would
          >be
          >in the same.
          >
          >Peace,
          >
          >--
          >Cameron Purdy
          >Tangosol, Inc.
          >http://www.tangosol.com
          >Tangosol Server: Enabling enterprise application customization
          >
          >
          >"Routis Haralampos" <[email protected]> wrote in message
          >news:[email protected]...
          >> Hi,
          >> Suppose that I a statefull session bean that uses a helper class to
          >delegate
          >> its business methods. If the transactions are demarcated from the
          >container
          >> will the transactional context of the caller (of the helper class)
          >method
          >be
          >> propagated to the helper class?
          >> Thank you in advance
          >>
          >>
          >
          >

Bug: weblogic.jar doesn't include the javax.ejb classes

In the
Oracle WebLogic Server 11gR1 (10.3.6) + Coherence -
Package Installer
the C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar doesn't include the javax.ejb package classes. The javax.ejb package is empty.

This is the correct behavior, stub and skeleton classes are generated at deployment time by WebLogic server and stored in a server internal location.
In case you are interested, it is something like: ...\samples\domains\medrec\servers\MedRecServer\cache\EJBCompilerCache\ with file named like HelloSession_gjfaqw_Intf.java., etc.
-danny

Context Propagation - Bug Weblogic 81 SP1

Similar Messages

Maybe you are looking for