April 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7654) Ickle parser should have a different representation for each literal type instead of using string for everything

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7654?page=com.atlassian.jira.plugin.... ] Work on ISPN-7654 started by Adrian Nistor. ------------------------------------------- > Ickle parser should have a different representation for each literal type instead of using string for everything > ---------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7654 > URL: https://issues.jboss.org/browse/ISPN-7654 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.1.0.Final > > > All constant literals regardless of type are represented as string now and are later parsed into integers, booleans, etc, when the query is translated. We should do this at the beginning phase of parsing. See ConstantLiteralTree class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7698) Administration console - minor issues with removing node

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7698?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7698. -------------------------------- Resolution: Done > Administration console - minor issues with removing node > -------------------------------------------------------- > > Key: ISPN-7698 > URL: https://issues.jboss.org/browse/ISPN-7698 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.0.1.Final > > > Removing node opens confirmation dialog which says: > Remove server new-node from undefined? > Suggested fix: > The node must be in stopped state to perform the operation so the cluster info is not available. The confirmation might just say: Remove server new-node? > After clicking confirm the Loading icon is displayed until users click on one of the tabs. (The node is successfully removed) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7698) Administration console - minor issues with removing node

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7698?page=com.atlassian.jira.plugin.... ] Ryan Emerson reassigned ISPN-7698: ---------------------------------- Assignee: Vladimir Blagojevic > Administration console - minor issues with removing node > -------------------------------------------------------- > > Key: ISPN-7698 > URL: https://issues.jboss.org/browse/ISPN-7698 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.0.1.Final > > > Removing node opens confirmation dialog which says: > Remove server new-node from undefined? > Suggested fix: > The node must be in stopped state to perform the operation so the cluster info is not available. The confirmation might just say: Remove server new-node? > After clicking confirm the Loading icon is displayed until users click on one of the tabs. (The node is successfully removed) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7698) Administration console - minor issues with removing node

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7698?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7698: ------------------------------- Fix Version/s: 9.0.1.Final > Administration console - minor issues with removing node > -------------------------------------------------------- > > Key: ISPN-7698 > URL: https://issues.jboss.org/browse/ISPN-7698 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.0.1.Final > > > Removing node opens confirmation dialog which says: > Remove server new-node from undefined? > Suggested fix: > The node must be in stopped state to perform the operation so the cluster info is not available. The confirmation might just say: Remove server new-node? > After clicking confirm the Loading icon is displayed until users click on one of the tabs. (The node is successfully removed) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7698) Administration console - minor issues with removing node

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7698?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7698: ------------------------------- Status: Open (was: New) > Administration console - minor issues with removing node > -------------------------------------------------------- > > Key: ISPN-7698 > URL: https://issues.jboss.org/browse/ISPN-7698 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.0.1.Final > > > Removing node opens confirmation dialog which says: > Remove server new-node from undefined? > Suggested fix: > The node must be in stopped state to perform the operation so the cluster info is not available. The confirmation might just say: Remove server new-node? > After clicking confirm the Loading icon is displayed until users click on one of the tabs. (The node is successfully removed) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7698) Administration console - minor issues with removing node

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7698?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7698: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/203 > Administration console - minor issues with removing node > -------------------------------------------------------- > > Key: ISPN-7698 > URL: https://issues.jboss.org/browse/ISPN-7698 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.0.1.Final > > > Removing node opens confirmation dialog which says: > Remove server new-node from undefined? > Suggested fix: > The node must be in stopped state to perform the operation so the cluster info is not available. The confirmation might just say: Remove server new-node? > After clicking confirm the Loading icon is displayed until users click on one of the tabs. (The node is successfully removed) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7713) LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-7713: ------------------------------------- Summary: LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction Key: ISPN-7713 URL: https://issues.jboss.org/browse/ISPN-7713 Project: Infinispan Issue Type: Bug Components: Security Reporter: Kamesh Sampath Priority: Critical When enabling security with Inifinispan with LDAP backend and when using `common-role-name-mapper` for authorisation, the extraction fails to extract the role name when the role name attribute e.g. "cn" is used instead of "CN" in the distinguished name. Its identified that the `org.infinispan.security.impl.CommonRoleMapper` use a case sensitive search and extracts roles only when the DN is like "CN=Developers,ou=Groups,dc=example,dc=com" The current workaround is to use the use a ldap authorization like {code:xml} <group-search group-name="SIMPLE" iterative="true" group-dn-attribute="dn" group-name-attribute="cn"> <group-to-principal search-by="DISTINGUISHED_NAME" base-dn="ou=Groups,dc=example,dc=com"> <membership-filter principal-attribute="uniqueMember"/> </group-to-principal> </group-search> {code} and define the cache-container authorisation like {code:xml} <security> <authorization>   <identity-role-mapper/> <role name="ClusterAdmins" permissions="ALL"/> <role name="Developers" permissions="WRITE"/> <role name="Business" permissions="READ"/> <role name="Managers" permissions="ALL_READ ALL_WRITE"/> </authorization> </security> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7712) LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7712?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7712: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5066 > LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction > ------------------------------------------------------------------------- > > Key: ISPN-7712 > URL: https://issues.jboss.org/browse/ISPN-7712 > Project: Infinispan > Issue Type: Bug > Components: Security > Reporter: Kamesh Sampath > Priority: Critical > Labels: ldap, ldap-realm, role-mapping > Attachments: example.com.ldif, jdg-security-demo.tar.gz, ldap_cluster_notworking.xml, ldap_cluster_workaround.xml > > > When enabling security with Inifinispan with LDAP backend and when using `common-role-name-mapper` for authorisation, the extraction fails to extract the role name when the role name attribute e.g. "cn" is used instead of "CN" in the distinguished name. > Its identified that the `org.infinispan.security.impl.CommonRoleMapper` use a case sensitive search and extracts roles only when the DN is like "CN=Developers,ou=Groups,dc=example,dc=com" > The current workaround is to use the use a ldap authorization like > {code:xml} > <group-search group-name="SIMPLE" iterative="true" group-dn-attribute="dn" group-name-attribute="cn"> > <group-to-principal search-by="DISTINGUISHED_NAME" base-dn="ou=Groups,dc=example,dc=com"> > <membership-filter principal-attribute="uniqueMember"/> > </group-to-principal> > </group-search> > {code} > and define the cache-container authorisation like > {code:xml} > <security> > <authorization> >  >  > <identity-role-mapper/> > <role name="ClusterAdmins" permissions="ALL"/> > <role name="Developers" permissions="WRITE"/> > <role name="Business" permissions="READ"/> > <role name="Managers" permissions="ALL_READ ALL_WRITE"/> > </authorization> > </security> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7712) LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7712?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7712: ---------------------------------- Status: Open (was: New) > LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction > ------------------------------------------------------------------------- > > Key: ISPN-7712 > URL: https://issues.jboss.org/browse/ISPN-7712 > Project: Infinispan > Issue Type: Bug > Components: Security > Reporter: Kamesh Sampath > Priority: Critical > Labels: ldap, ldap-realm, role-mapping > Attachments: example.com.ldif, jdg-security-demo.tar.gz, ldap_cluster_notworking.xml, ldap_cluster_workaround.xml > > > When enabling security with Inifinispan with LDAP backend and when using `common-role-name-mapper` for authorisation, the extraction fails to extract the role name when the role name attribute e.g. "cn" is used instead of "CN" in the distinguished name. > Its identified that the `org.infinispan.security.impl.CommonRoleMapper` use a case sensitive search and extracts roles only when the DN is like "CN=Developers,ou=Groups,dc=example,dc=com" > The current workaround is to use the use a ldap authorization like > {code:xml} > <group-search group-name="SIMPLE" iterative="true" group-dn-attribute="dn" group-name-attribute="cn"> > <group-to-principal search-by="DISTINGUISHED_NAME" base-dn="ou=Groups,dc=example,dc=com"> > <membership-filter principal-attribute="uniqueMember"/> > </group-to-principal> > </group-search> > {code} > and define the cache-container authorisation like > {code:xml} > <security> > <authorization> >  >  > <identity-role-mapper/> > <role name="ClusterAdmins" permissions="ALL"/> > <role name="Developers" permissions="WRITE"/> > <role name="Business" permissions="READ"/> > <role name="Managers" permissions="ALL_READ ALL_WRITE"/> > </authorization> > </security> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7712) LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction

by Kamesh Sampath (JIRA)

Kamesh Sampath created ISPN-7712: ------------------------------------ Summary: LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction Key: ISPN-7712 URL: https://issues.jboss.org/browse/ISPN-7712 Project: Infinispan Issue Type: Bug Components: Security Reporter: Kamesh Sampath Priority: Critical Attachments: example.com.ldif, jdg-security-demo.tar.gz, ldap_cluster_notworking.xml, ldap_cluster_workaround.xml When enabling security with Inifinispan with LDAP backend and when using `common-role-name-mapper` for authorisation, the extraction fails to extract the role name when the role name attribute e.g. "cn" is used instead of "CN" in the distinguished name. Its identified that the `org.infinispan.security.impl.CommonRoleMapper` use a case sensitive search and extracts roles only when the DN is like "CN=Developers,ou=Groups,dc=example,dc=com" The current workaround is to use the use a ldap authorization like {code:xml} <group-search group-name="SIMPLE" iterative="true" group-dn-attribute="dn" group-name-attribute="cn"> <group-to-principal search-by="DISTINGUISHED_NAME" base-dn="ou=Groups,dc=example,dc=com"> <membership-filter principal-attribute="uniqueMember"/> </group-to-principal> </group-search> {code} and define the cache-container authorisation like {code:xml} <security> <authorization>   <identity-role-mapper/> <role name="ClusterAdmins" permissions="ALL"/> <role name="Developers" permissions="WRITE"/> <role name="Business" permissions="READ"/> <role name="Managers" permissions="ALL_READ ALL_WRITE"/> </authorization> </security> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2017