[JBoss JIRA] (GTNPORTAL-3457) Unify gatein jgroups configurations
by Lucas Ponce (JIRA)
Lucas Ponce created GTNPORTAL-3457:
--------------------------------------
Summary: Unify gatein jgroups configurations
Key: GTNPORTAL-3457
URL: https://issues.jboss.org/browse/GTNPORTAL-3457
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Lucas Ponce
Assignee: Lucas Ponce
GateIn cluster configuration is defined under:
./gatein/gatein.ear/portal.war/WEB-INF/classes/jgroups/ folder.
There are two separate jgroups configurations for exo.jcr and idm subsystems that can be merged into one.
Also, some properties has to be reviewed, as binding ips and enable_diagnostics.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3448) Failed authentication on service REST after a session timeout
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3448?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3448:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Failed authentication on service REST after a session timeout
> -------------------------------------------------------------
>
> Key: GTNPORTAL-3448
> URL: https://issues.jboss.org/browse/GTNPORTAL-3448
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Tuyen Nguyen The
> Assignee: Tuyen Nguyen The
> Fix For: 3.5.10.Final, 3.7.1.Final, 3.8.0.Final
>
> Attachments: authenticate-successfully.png, reauthenticated-failure.png
>
>
> Case to reproduce:
> - Access to api
> {code}
> http://localhost:8080/rest/private/managed-components/api/sites/classic/p...
> {code}
> - Authentication with user root and now we can list all page of classic site (include Group Navitation and Portal Navigation page)
> - Wait until session timeout (about ~30 minute)
> - Access to list all page api again, now we only see public pages (see attachments) and has error in log:
> {code}
> [http-bio-8080-exec-10] ERROR exo.core.component.security.core.SetCurrentIdentityFilter - Not found identity in IdentityRegistry for user root, check Login Module.
> {code}
> This error is unusually occured.
> Maybe identity was removed from IdentityRegistry after session timeout and it throw this error.
> So, we should set restoreIdentity=true of the filter "SetCurrentIdentityFilter" into web.xml of rest.war (like in portal.war) to reinject the identity when it is lost
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3448) Failed authentication on service REST after a session timeout
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3448?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3448:
----------------------------------
Fix Version/s: 3.5.10.Final
3.7.1.Final
3.8.0.Final
> Failed authentication on service REST after a session timeout
> -------------------------------------------------------------
>
> Key: GTNPORTAL-3448
> URL: https://issues.jboss.org/browse/GTNPORTAL-3448
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Tuyen Nguyen The
> Assignee: Tuyen Nguyen The
> Fix For: 3.5.10.Final, 3.7.1.Final, 3.8.0.Final
>
> Attachments: authenticate-successfully.png, reauthenticated-failure.png
>
>
> Case to reproduce:
> - Access to api
> {code}
> http://localhost:8080/rest/private/managed-components/api/sites/classic/p...
> {code}
> - Authentication with user root and now we can list all page of classic site (include Group Navitation and Portal Navigation page)
> - Wait until session timeout (about ~30 minute)
> - Access to list all page api again, now we only see public pages (see attachments) and has error in log:
> {code}
> [http-bio-8080-exec-10] ERROR exo.core.component.security.core.SetCurrentIdentityFilter - Not found identity in IdentityRegistry for user root, check Login Module.
> {code}
> This error is unusually occured.
> Maybe identity was removed from IdentityRegistry after session timeout and it throw this error.
> So, we should set restoreIdentity=true of the filter "SetCurrentIdentityFilter" into web.xml of rest.war (like in portal.war) to reinject the identity when it is lost
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3247) [IE8] Impossible to edit page containing accent character in its name
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3247?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3247:
----------------------------------
Fix Version/s: 3.5.10.Final
(was: 3.5.9.Final)
> [IE8] Impossible to edit page containing accent character in its name
> ---------------------------------------------------------------------
>
> Key: GTNPORTAL-3247
> URL: https://issues.jboss.org/browse/GTNPORTAL-3247
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Son Tran
> Assignee: Trong Tran
> Priority: Minor
> Labels: backlogs
> Fix For: 3.5.10.Final, 3.7.0.Final
>
>
> Using *IE8*, it's not possible to edit a page that contains an accented character in its name.
> Try to follow these steps to reproduce:
> - login to acme site.
> - Edit-> Page-> Add page
> - put the name " accentué"
> - Save the page, it is created and accessible (navigate to the page)
> - Select Edit-> Page-> Layout => nothing happens.
> we can not edit the page .
> With chrome and FF this works well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3253) [IE] Ajax requests are broken if the node name containing accent characters
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3253?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3253:
----------------------------------
Fix Version/s: 3.5.10.Final
(was: 3.5.9.Final)
> [IE] Ajax requests are broken if the node name containing accent characters
> ---------------------------------------------------------------------------
>
> Key: GTNPORTAL-3253
> URL: https://issues.jboss.org/browse/GTNPORTAL-3253
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Internet Explorer browser
> Reporter: Trong Tran
> Assignee: Hai Nguyen
> Priority: Critical
> Labels: backlogs
> Fix For: 3.5.10.Final, 3.7.0.Final
>
>
> h3. Problem
> Let's say we have a page with node name is "tét". Go to Edit Page, then click on the close/save button ==> it doesn't work.
> h3. Cause
> The encoded URI in the href attribute of <a> tag is automatically decoded in wrong ISO-8859-1 before the javascript function is executed
> h3. Proposal to fix the problem
> We should use *onclick* to perform the javascript ajax update execution instead of href attribute.
> Moreover, putting javascript code into href is kind of bad practice that we could avoid in use
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3410) Templates-cache is not share between nodes in cluster
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3410?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3410:
----------------------------------
Fix Version/s: 3.5.10.Final
(was: 3.5.9.Final)
> Templates-cache is not share between nodes in cluster
> -----------------------------------------------------
>
> Key: GTNPORTAL-3410
> URL: https://issues.jboss.org/browse/GTNPORTAL-3410
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Tuyen Nguyen The
> Assignee: Tuyen Nguyen The
> Fix For: 3.5.10.Final, 3.7.1.Final, 3.8.0.Final
>
>
> Start by setting up a cluster environement with two nodes and start the nodes
> In Node 1:
> - Goto Sitemap page
> - Use editor to edit UISitemapTree.gtmpl
> - Goto sitemap page, it still old template because template is cached.
> - Use template management MBean to clear cache in node1
> - Goto sitemap page again and we see the change
> In Node 2:
> - Goto sitemap page
> => NOK: sitemap page in node 2 still use old template
> OK: template cache in 2 node must the same
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months