(Note, this has nothing to do with the JSS SSO Plugin - it's morphed
into a BMC Mid Tier defect.)
Abhijit,
Not only is this thread months old, your response is wrong.
> The Container is adding a Cookie with the default Context Path as “/” which
> is referred as the poison Cookie in
> this threa
The Container is adding a Cookie with the default Context Path as “/” which is
referred as the poison Cookie in this thread.
Mid-Tier sets JSessionID Cookie marked as HTTPOnly with the right Context Path.
In this case one needs to do the right settings with the Container to let it
know that JSes
The same issue exists for WebSphere as well.
Axton Grams
On Tue, Jun 10, 2014 at 3:21 PM, John Baker
wrote:
> Hello,
>
> So let me answer this query, as it's related to a piece of non-optimal
> design in Mid Tier that only raises its head in some circumstances. JSS
> worked with another custom
Hello,
So let me answer this query, as it's related to a piece of non-optimal
design in Mid Tier that only raises its head in some circumstances. JSS
worked with another customer (ie not Frank) to diagnose this issue in
early May, and reported the issue to the BMC Premier Support team.
The c
ITSM 764 sp2. Weblogic 10.3, RHEL
Can anyone share their experience using the JSS-SSO plugin under Weblogic? The
product is installed in our development environment and is working perfectly;
configuration was minimal and support has been very good. We are utilizing
Windows Authentication with K
5 matches
Mail list logo
