[JBoss JIRA] (GTNPORTAL-3505) WSRP Producers behind Load Balancers get wrong endpoint URL
by Juraci Paixão Kröhling (JIRA)
Juraci Paixão Kröhling created GTNPORTAL-3505:
-------------------------------------------------
Summary: WSRP Producers behind Load Balancers get wrong endpoint URL
Key: GTNPORTAL-3505
URL: https://issues.jboss.org/browse/GTNPORTAL-3505
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Juraci Paixão Kröhling
Assignee: Juraci Paixão Kröhling
When the WSRP producers are behind a cluster, the address generated on the SOAP message is based on the node's address/port, and not the cluster's. BZ 880729 and 1102733.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (GTNPORTAL-3493) Membership just added, disappears
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3493?page=com.atlassian.jira.pl... ]
Marek Posolda updated GTNPORTAL-3493:
-------------------------------------
Fix Version/s: 3.8.3.Final
3.9.0.Final
Assignee: Marek Posolda
Affects Version/s: (was: 3.5.9.Final)
> Membership just added, disappears
> ---------------------------------
>
> Key: GTNPORTAL-3493
> URL: https://issues.jboss.org/browse/GTNPORTAL-3493
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Boubaker Khanfir
> Assignee: Marek Posolda
> Fix For: 3.8.3.Final, 3.9.0.Final
>
> Attachments: plidm-ldap-membership-disappear.zip
>
>
> I attach a new unit test for a bug that we met in GateIN 3.5 (PL IDM 1.4.4).
> This one shows how we can add a membership and just after that it disappears.
> In this file [idm-configuration.xml|https://github.com/gatein/gatein-portal/blob/3.5.x/...], the comment :
> {quote}
> <!-- if "associationMembershipType" option is used and this option is set to true
> then Membership with MembershipType configured to be stored as PicketLink IDM association
> will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
> For RW LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
> However for DB only and/or Read-only LDAP, it's recommended to not map anything here -->
> {quote}
> is not good and have to be like this:
> {quote}
> <!-- if "associationMembershipType" option is used and this option is set to true
> then Membership with MembershipType configured to be stored as PicketLink IDM association
> will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
> For LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
> However for DB only, it's recommended to not map anything here -->
> {quote}
> What changes in this comment ?
> The LDAP RW or ReadOnly have to get the same behavior using this parameter and we should map all LDAP groups in "ignoreMappedMembershipTypeGroupList".
> I think it's better to force/compute this parameter in OrganizationService instead of giving the ability to do it manually. The other solution is to modify OrganizationService Impl to deal with such a use case but I prefer the first choice.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (GTNPORTAL-3493) Membership just added, disappears
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3493?page=com.atlassian.jira.pl... ]
Marek Posolda updated GTNPORTAL-3493:
-------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/869
Sent PR with small update for ignoreMappedMembershipTypeGroupList property
> Membership just added, disappears
> ---------------------------------
>
> Key: GTNPORTAL-3493
> URL: https://issues.jboss.org/browse/GTNPORTAL-3493
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Boubaker Khanfir
> Fix For: 3.8.3.Final, 3.9.0.Final
>
> Attachments: plidm-ldap-membership-disappear.zip
>
>
> I attach a new unit test for a bug that we met in GateIN 3.5 (PL IDM 1.4.4).
> This one shows how we can add a membership and just after that it disappears.
> In this file [idm-configuration.xml|https://github.com/gatein/gatein-portal/blob/3.5.x/...], the comment :
> {quote}
> <!-- if "associationMembershipType" option is used and this option is set to true
> then Membership with MembershipType configured to be stored as PicketLink IDM association
> will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
> For RW LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
> However for DB only and/or Read-only LDAP, it's recommended to not map anything here -->
> {quote}
> is not good and have to be like this:
> {quote}
> <!-- if "associationMembershipType" option is used and this option is set to true
> then Membership with MembershipType configured to be stored as PicketLink IDM association
> will not be stored as PicketLink IDM Role in case that they are in groups from this parameter.
> For LDAP setup, it's recommended to map all groups mapped to LDAP (all those from parameter groupTypeMappings)
> However for DB only, it's recommended to not map anything here -->
> {quote}
> What changes in this comment ?
> The LDAP RW or ReadOnly have to get the same behavior using this parameter and we should map all LDAP groups in "ignoreMappedMembershipTypeGroupList".
> I think it's better to force/compute this parameter in OrganizationService instead of giving the ability to do it manually. The other solution is to modify OrganizationService Impl to deal with such a use case but I prefer the first choice.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (GTNPORTAL-3495) Membership Pagination don't work
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3495?page=com.atlassian.jira.pl... ]
Marek Posolda updated GTNPORTAL-3495:
-------------------------------------
Fix Version/s: 3.8.3.Final
3.9.0.Final
> Membership Pagination don't work
> --------------------------------
>
> Key: GTNPORTAL-3495
> URL: https://issues.jboss.org/browse/GTNPORTAL-3495
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.9.Final
> Reporter: Boubaker Khanfir
> Assignee: Marek Posolda
> Fix For: 3.8.3.Final, 3.9.0.Final
>
> Attachments: plidm-ldap-membership-pagination.zip
>
>
> I attach a new unit test for a bug that I met in PL IDM 1.4.4.
> Test case description:
> 1/ add about 10 users in an LDAP group
> 2/ use SearchCriteria to paginate on the Members of this group
> => Problem: pagination doesn't work
> Why does it fails:
> Because in this method "org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl.resolveRelationships(IdentityStoreInvocationContext, IdentityObject, IdentityObjectRelationshipType, boolean, boolean, String, IdentityObjectSearchCriteria)" the attribute "IdentityObjectSearchCriteria" isn't used for pagination.
> To workaround this bug I had to use (skipPaginationInMembershipQuery=true). If the UI is buggy without this parameter to "true", I think it has to be *by default "true" in Config class* and may be even delete this option to not use pagination in Membership at all.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (GTNPORTAL-3495) Membership Pagination don't work
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3495?page=com.atlassian.jira.pl... ]
Marek Posolda commented on GTNPORTAL-3495:
------------------------------------------
Sent PR with small update of comment for "skipPaginationInMembershipQuery" property
> Membership Pagination don't work
> --------------------------------
>
> Key: GTNPORTAL-3495
> URL: https://issues.jboss.org/browse/GTNPORTAL-3495
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.9.Final
> Reporter: Boubaker Khanfir
> Assignee: Marek Posolda
> Fix For: 3.8.3.Final, 3.9.0.Final
>
> Attachments: plidm-ldap-membership-pagination.zip
>
>
> I attach a new unit test for a bug that I met in PL IDM 1.4.4.
> Test case description:
> 1/ add about 10 users in an LDAP group
> 2/ use SearchCriteria to paginate on the Members of this group
> => Problem: pagination doesn't work
> Why does it fails:
> Because in this method "org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl.resolveRelationships(IdentityStoreInvocationContext, IdentityObject, IdentityObjectRelationshipType, boolean, boolean, String, IdentityObjectSearchCriteria)" the attribute "IdentityObjectSearchCriteria" isn't used for pagination.
> To workaround this bug I had to use (skipPaginationInMembershipQuery=true). If the UI is buggy without this parameter to "true", I think it has to be *by default "true" in Config class* and may be even delete this option to not use pagination in Membership at all.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (GTNPORTAL-3495) Membership Pagination don't work
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3495?page=com.atlassian.jira.pl... ]
Marek Posolda updated GTNPORTAL-3495:
-------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/869
> Membership Pagination don't work
> --------------------------------
>
> Key: GTNPORTAL-3495
> URL: https://issues.jboss.org/browse/GTNPORTAL-3495
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.9.Final
> Reporter: Boubaker Khanfir
> Assignee: Marek Posolda
> Fix For: 3.8.3.Final, 3.9.0.Final
>
> Attachments: plidm-ldap-membership-pagination.zip
>
>
> I attach a new unit test for a bug that I met in PL IDM 1.4.4.
> Test case description:
> 1/ add about 10 users in an LDAP group
> 2/ use SearchCriteria to paginate on the Members of this group
> => Problem: pagination doesn't work
> Why does it fails:
> Because in this method "org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl.resolveRelationships(IdentityStoreInvocationContext, IdentityObject, IdentityObjectRelationshipType, boolean, boolean, String, IdentityObjectSearchCriteria)" the attribute "IdentityObjectSearchCriteria" isn't used for pagination.
> To workaround this bug I had to use (skipPaginationInMembershipQuery=true). If the UI is buggy without this parameter to "true", I think it has to be *by default "true" in Config class* and may be even delete this option to not use pagination in Membership at all.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months