[JBoss JIRA] (GTNPORTAL-2979) WSRP should be configured by default to transmit user identification using WS-Security
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2979?page=com.atlassian.jira.pl... ]
Marek Posolda updated GTNPORTAL-2979:
-------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> WSRP should be configured by default to transmit user identification using WS-Security
> --------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2979
> URL: https://issues.jboss.org/browse/GTNPORTAL-2979
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: WSRP integration
> Affects Versions: 3.6.0.Beta01
> Reporter: Chris Laprun
> Assignee: Chris Laprun
> Priority: Minor
> Fix For: 3.6.0.Beta02
>
>
> Transmission of user identification data is not activated by default, just configured. Transmitting user data will still require to activate the WS-Security option on the consumer's configuration page in the admin interface or via wsrp-consumers-config.xml.
> Note also that full security will not be achieved without using SSL or message-level encryption but this is no worse than how, by default, GateIn already transmit user data over clear channels. This change just removes one configuration steps from the process of fully securing WSRP with WS-Security.
--
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
11 years, 9 months
[JBoss JIRA] (GTNPORTAL-2980) Improved Modularization
by Marko Strukelj (JIRA)
Marko Strukelj created GTNPORTAL-2980:
-----------------------------------------
Summary: Improved Modularization
Key: GTNPORTAL-2980
URL: https://issues.jboss.org/browse/GTNPORTAL-2980
Project: GateIn Portal
Issue Type: Enhancement
Affects Versions: 3.6.0.Beta01
Reporter: Marko Strukelj
Assignee: Marko Strukelj
Fix For: 3.6.0.Beta02
Module org.gatein.lib contains many third party libraries, and exports some of the libraries as well.
This may cause class-loading issues for user applications, as there are important integration APIs exposed to apps via org.gatein.lib.
Improvement would not expose any third party library, but only gatein libraries.
--
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
11 years, 9 months
[JBoss JIRA] (GTNPORTAL-2820) Unable to clone page (PageService) in a different destination
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2820?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-2820:
----------------------------------------------------
Martin Weiler <mweiler(a)redhat.com> made a comment on [bug 916260|https://bugzilla.redhat.com/show_bug.cgi?id=916260]
Attaching a fixed version of the reproducer. The key is to create a cloned page with the same name, but in a different destination folder:
SiteKey srcSiteKey = new SiteKey(SiteType.PORTAL, "classic");
PageKey srcPage = new PageKey(srcSiteKey, "homepage");
// destination
SiteKey dstSiteKey = new SiteKey(SiteType.GROUP, "/platform/users");
pageService.clone(srcPage, dstSiteKey.page(srcPage.getName()));
output = "Page " + srcPage + " cloned with success to " + dstSiteKey;
Note that you can only successfully invoke the portlet once.
> Unable to clone page (PageService) in a different destination
> -------------------------------------------------------------
>
> Key: GTNPORTAL-2820
> URL: https://issues.jboss.org/browse/GTNPORTAL-2820
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Java API
> Affects Versions: 3.5.0.Final
> Environment: Gatein 3.5.2 Final
> Reporter: Gregory SEBERT
> Assignee: Boleslaw Dawidowicz
> Fix For: 3.6.0.Beta01
>
>
> In the PageManagement service, when I clone a page to a different destination, I received an exception :
> "Could not clone page " + dst.name + "to existing page " + dst.site.getType() + " with id " + dst.site.getName());
> I have a look at the implementation, I find a typo mistake on line 273:
> org.gatein.mop.api.workspace.Page dstRoot = srcSite.getRootPage();
> It should be :
> org.gatein.mop.api.workspace.Page dstRoot = dstSite.getRootPage();
> Best regards,
> Grégory
--
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
11 years, 9 months
[JBoss JIRA] (GTNPORTAL-2979) WSRP should be configured by default to transmit user identification using WS-Security
by Chris Laprun (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2979?page=com.atlassian.jira.pl... ]
Chris Laprun updated GTNPORTAL-2979:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/437
> WSRP should be configured by default to transmit user identification using WS-Security
> --------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2979
> URL: https://issues.jboss.org/browse/GTNPORTAL-2979
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: WSRP integration
> Affects Versions: 3.6.0.Beta01
> Reporter: Chris Laprun
> Assignee: Chris Laprun
> Priority: Minor
> Fix For: 3.6.0.Beta02
>
>
> Transmission of user identification data is not activated by default, just configured. Transmitting user data will still require to activate the WS-Security option on the consumer's configuration page in the admin interface or via wsrp-consumers-config.xml.
> Note also that full security will not be achieved without using SSL or message-level encryption but this is no worse than how, by default, GateIn already transmit user data over clear channels. This change just removes one configuration steps from the process of fully securing WSRP with WS-Security.
--
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
11 years, 9 months
[JBoss JIRA] (GTNPORTAL-2820) Unable to clone page (PageService) in a different destination
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2820?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-2820:
----------------------------------------------------
Martin Weiler <mweiler(a)redhat.com> made a comment on [bug 916260|https://bugzilla.redhat.com/show_bug.cgi?id=916260]
The reproducer portlet has the following error:
SiteKey siteKey = new SiteKey(SiteType.GROUP, "/platform/users");
should be replaced by:
SiteKey siteKey = new SiteKey(SiteType.PORTAL, "classic");
otherwise the portlet fails to find the src page.
> Unable to clone page (PageService) in a different destination
> -------------------------------------------------------------
>
> Key: GTNPORTAL-2820
> URL: https://issues.jboss.org/browse/GTNPORTAL-2820
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Java API
> Affects Versions: 3.5.0.Final
> Environment: Gatein 3.5.2 Final
> Reporter: Gregory SEBERT
> Assignee: Boleslaw Dawidowicz
> Fix For: 3.6.0.Beta01
>
>
> In the PageManagement service, when I clone a page to a different destination, I received an exception :
> "Could not clone page " + dst.name + "to existing page " + dst.site.getType() + " with id " + dst.site.getName());
> I have a look at the implementation, I find a typo mistake on line 273:
> org.gatein.mop.api.workspace.Page dstRoot = srcSite.getRootPage();
> It should be :
> org.gatein.mop.api.workspace.Page dstRoot = dstSite.getRootPage();
> Best regards,
> Grégory
--
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
11 years, 9 months