Hi Ayesha,
Issue came with logout operation, but host name was set to localhost.
Anyway, I updated jaggery.js version to latest (0.12.2) and issue seems to
be sorted with that. Thanks for checking.
Regards,
Dinusha.
On Mon, Feb 22, 2016 at 4:49 PM, Ayesha Dissanayaka wrote:
> Hi Dinusha,
>
> j
Hi Dinusha,
jaggery 0.12.0 should be fine, since it has pretty much the same jaggery
code content as of jaggery-0.11.2 which is used in greg-5.1.0. However, we
couldn't completely resolve the issues in some edge cases at
login/logout[2] such as, accessing store/publisher with IP instead of
domain
Hi Ayesha,
Is there a released version available now with the above fix ? Getting same
issue in AppM with jaggery.js.feature-0.12.0.
Regards,
Dinusha.
On Wed, Oct 28, 2015 at 11:21 AM, Ayesha Dissanayaka
wrote:
> Hi,
>
> On Tue, Oct 27, 2015 at 5:53 PM, Manuranga Perera wrote:
>
>>
>> add log
Hi,
On Tue, Oct 27, 2015 at 5:53 PM, Manuranga Perera wrote:
>
> add logic to check if instance of session object and set it to session obj
> if true else set to request obj
>
Chanaka and myself tested this fix and it works as expected.
Greg team will continue further testing the login/logout s
fix:
inSessionHostObject java class, in jsConstructor method, change
if (!(args[0] instanceof HttpServletRequest)) {
HostObjectUtil.getReservedHostObjectWarn(hostObjectName);
}
add logic to check if instance of session object and set it to session obj
if true else set to request obj
--
W
The initial issue Chandana has mentioned is fixed by the commit to acs.jag.
Now the issue is is with session.invalidate method. Following is the
exception. Tried to catch the exception from the session host object but
didn't work. Following is the stack trace.
[2015-10-27 17:35:39,036] WARN
{org
Hi Chandana,
On Tue, Oct 27, 2015 at 12:33 PM, Chandana Napagoda
wrote:
> Hi Udara,
>
> Changing host name using carbon.xml will not work, since it will break the
> subscriptions and notifications.
>
> I have checked with Chanaka's fix, but it doesn't resolve the complete
> story. When user clic
Hi Udara,
Changing host name using carbon.xml will not work, since it will break the
subscriptions and notifications.
I have checked with Chanaka's fix, but it doesn't resolve the complete
story. When user clicks on the Logout link in the Store, it still throws
same exception I have pointed in my
Hi Chandana,
Please check whether we are shifting host name in this process, eg :- IP to
Host or vice versa.
If this is the problem we can avoid by using consistent host-name.
Anyway noticed that Chanaka solving this issue by not using session to
store relaystate. Hope this will solve this proble
Hi Udara,
I am not clicking on "Go to Store" link shown in the publisher. Steps I am
following are as below.
- Go to Store URL and access it through anonymous mode.
- Then access the Publisher URL in a different tab of the same browser.
- Then log into Publisher app and navigate to Stor
Hi All,
As we understood this happens only when we navigate to the store via "Go to
Store" link which is provided by GREG extensions.
Problem here is you are initially logging in to the publisher using
hostname "localhost" and then redirect to the store using IP.
In publisher.json you have define
Hi Udara,
Here are the steps to reproduce this issue:
1). Unzip G-Reg 5.1.0-SNAPSHOT pack an start it.
2). Load Store and Publisher sites in the same browser, different tabs.
3). Login to the publisher and perform some operations.
4). Then navigate to Store tab and click on Signin link. Then a 50
Hi Chandana,
Had a look at this in a ES pack with all latest fixes done for (jaggeryapps
+ jaggery-extensions[1]), But haven't face such issue. Let me know the
exact steps to reproduce.
[1]
https://github.com/wso2/jaggery-extensions/commit/6a572c32de0b4f2ab9a1e52a3b5c62af5f7294a6
Regards,
UdaraR
Hi ES team,
With the latest carbon store changes, we have noticed that if the very
first logged in user first access the publisher and then login to store
using SSO, an exception is logged. Further if user click on logout, again
another exception is logged. Is this errors occurring due to recent S
14 matches
Mail list logo
