March 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3402) Allow customers to customize login validation and accounts expiration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3402?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3402: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=973835, https://bugzilla.redhat.com/show_bug.cgi?id=1072150 (was: https://bugzilla.redhat.com/show_bug.cgi?id=973835) > Allow customers to customize login validation and accounts expiration > ---------------------------------------------------------------------- > > Key: GTNPORTAL-3402 > URL: https://issues.jboss.org/browse/GTNPORTAL-3402 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > > Allow customers to add custom password rules to their GateIn installations. > We've had a discussion about the possibilities, and it seems that the best for now would be something as follows: > 1) Adapt/extend the current UserConfigurableValidator, which allows the usage of min/max/regex constraints for values based on values from a configuration file, for instance: > gatein.validators.mycompanypasspolicy.length.min=5 > gatein.validators.mycompanypasspolicy.length.max=50 > gatein.validators.mycompanypasspolicy.regexp=... > 2) Extend the User Interface to allow the administrator to enter the name of the configuration entry related to the password policy (mycompanypasspolicy , in this case). > (originally requested via Bugzilla #973835) -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3404: ---------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Priority: Minor > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > <infinispan > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > <global> > <evictionScheduledExecutor factory="org.infinispan.executors.DefaultScheduledExecutorFactory"> > <properties> > <property name="threadNamePrefix" value="EvictionThread"/> > </properties> > </evictionScheduledExecutor> > <globalJmxStatistics jmxDomain="platform.insp.cache.indexer" enabled="true" allowDuplicateDomains="true"/> > <transport transportClass="org.infinispan.remoting.transport.jgroups.JGroupsTransport" clusterName="${infinispan-cluster-name}" distributedSyncTimeout="20000"> > <properties> > <property name="configurationFile" value="${gatein.jcr.jgroups.config}"/> > </properties> > </transport> > </global> > <default> > <clustering mode="replication"> > <stateTransfer timeout="20000" fetchInMemoryState="false" /> > <sync replTimeout="20000"/> > </clustering> > <locking isolationLevel="READ_COMMITTED" lockAcquisitionTimeout="20000" writeSkewCheck="false" concurrencyLevel="500" useLockStriping="false"/> > <transaction transactionManagerLookupClass="org.exoplatform.services.transaction.infinispan.JBossStandaloneJTAManagerLookup" syncRollbackPhase="true" syncCommitPhase="true" transactionMode="TRANSACTIONAL"/> > <jmxStatistics enabled="true"/> > <eviction strategy="NONE"/> > <loaders passivation="false" shared="false" preload="false"> > <loader class="${infinispan-cachestore-classname}" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false"> > <async enabled="false"/> > </loader> > </loaders> > </default> > </infinispan> > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3404) The path of JCr index cache is hard coded in configuration.properties

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3404?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3404: ---------------------------------- Sprint: Sprint 95 > The path of JCr index cache is hard coded in configuration.properties > --------------------------------------------------------------------- > > Key: GTNPORTAL-3404 > URL: https://issues.jboss.org/browse/GTNPORTAL-3404 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final > Reporter: Racha Touzi > Priority: Minor > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The path 's configuration of the JCR index cache is always configured in cluster mode "/conf/jcr/infinispan/cluster/indexer-config.xml" whatever the profil mode ( local or cluster) . > But in local mode we don't really need the transport configuration and the clustering configuration > {code} > <infinispan > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" > xmlns="urn:infinispan:config:5.2"> > <global> > <evictionScheduledExecutor factory="org.infinispan.executors.DefaultScheduledExecutorFactory"> > <properties> > <property name="threadNamePrefix" value="EvictionThread"/> > </properties> > </evictionScheduledExecutor> > <globalJmxStatistics jmxDomain="platform.insp.cache.indexer" enabled="true" allowDuplicateDomains="true"/> > <transport transportClass="org.infinispan.remoting.transport.jgroups.JGroupsTransport" clusterName="${infinispan-cluster-name}" distributedSyncTimeout="20000"> > <properties> > <property name="configurationFile" value="${gatein.jcr.jgroups.config}"/> > </properties> > </transport> > </global> > <default> > <clustering mode="replication"> > <stateTransfer timeout="20000" fetchInMemoryState="false" /> > <sync replTimeout="20000"/> > </clustering> > <locking isolationLevel="READ_COMMITTED" lockAcquisitionTimeout="20000" writeSkewCheck="false" concurrencyLevel="500" useLockStriping="false"/> > <transaction transactionManagerLookupClass="org.exoplatform.services.transaction.infinispan.JBossStandaloneJTAManagerLookup" syncRollbackPhase="true" syncCommitPhase="true" transactionMode="TRANSACTIONAL"/> > <jmxStatistics enabled="true"/> > <eviction strategy="NONE"/> > <loaders passivation="false" shared="false" preload="false"> > <loader class="${infinispan-cachestore-classname}" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false"> > <async enabled="false"/> > </loader> > </loaders> > </default> > </infinispan> > {code} > So , The configuration of JCR Index cache must be one for local mode and one for Cluster mode , > the path must be > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/${gatein.jcr.config.type}/indexer-config.xml > {code} > instead of > {code} > gatein.jcr.index.cache.config=war:/conf/jcr/infinispan/cluster/indexer-config.xml > {code} -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3363) Provide feedback on logs when gadget is not white-listed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3363?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3363: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=794468, https://bugzilla.redhat.com/show_bug.cgi?id=1072147 (was: https://bugzilla.redhat.com/show_bug.cgi?id=794468) > Provide feedback on logs when gadget is not white-listed > -------------------------------------------------------- > > Key: GTNPORTAL-3363 > URL: https://issues.jboss.org/browse/GTNPORTAL-3363 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.7.0.Final > > > When a gadget is not white-listed, the ProxyFilterService rejects the loading of the contents, but provides no hints on the logs about it, making the user to believe that the gadget might be at fault. A solution is to log at INFO level that access to it has been blocked. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3361) Allow more flexible cache-control header per portal

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3361?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3361: ---------------------------------------------------- Jared MORGAN <jmorgan(a)redhat.com> changed the Status of [bug 1072146|https://bugzilla.redhat.com/show_bug.cgi?id=1072146] from NEW to ASSIGNED > Allow more flexible cache-control header per portal > --------------------------------------------------- > > Key: GTNPORTAL-3361 > URL: https://issues.jboss.org/browse/GTNPORTAL-3361 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.7.0.Final > > > Allow each portal to have its own Cache-control directive, as per Bugzilla 811126 -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3361) Allow more flexible cache-control header per portal

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3361?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3361: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=811126, https://bugzilla.redhat.com/show_bug.cgi?id=1072146 (was: https://bugzilla.redhat.com/show_bug.cgi?id=811126) > Allow more flexible cache-control header per portal > --------------------------------------------------- > > Key: GTNPORTAL-3361 > URL: https://issues.jboss.org/browse/GTNPORTAL-3361 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.7.0.Final > > > Allow each portal to have its own Cache-control directive, as per Bugzilla 811126 -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3369) Add Public Render Parameter support at URL level

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3369?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3369: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=793726, https://bugzilla.redhat.com/show_bug.cgi?id=1072145 (was: https://bugzilla.redhat.com/show_bug.cgi?id=793726) > Add Public Render Parameter support at URL level > ------------------------------------------------ > > Key: GTNPORTAL-3369 > URL: https://issues.jboss.org/browse/GTNPORTAL-3369 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebUI > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.0.Final > > > Add support to pass Public Render Parameters at URL level -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3362) Add examples for Inter Portlet Communication

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3362?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3362: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=793726, https://bugzilla.redhat.com/show_bug.cgi?id=1072145 (was: https://bugzilla.redhat.com/show_bug.cgi?id=793726) > Add examples for Inter Portlet Communication > -------------------------------------------- > > Key: GTNPORTAL-3362 > URL: https://issues.jboss.org/browse/GTNPORTAL-3362 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.7.0.Final > > > Add examples covering Public Render Parameters and Portlet Events -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3409) Use of legacy html attributes not compliant

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3409?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3409: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1066001 > Use of legacy html attributes not compliant > ------------------------------------------- > > Key: GTNPORTAL-3409 > URL: https://issues.jboss.org/browse/GTNPORTAL-3409 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > > GateIn produces XHTML 1.0 Strict type documents. > There are some legacy html elements (i.e. target="_blank") not compatible with XHTML 1.0 Strict type document creating a non compliant markup. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3409) Use of legacy html attributes not compliant

by Lucas Ponce (JIRA)

Lucas Ponce created GTNPORTAL-3409: -------------------------------------- Summary: Use of legacy html attributes not compliant Key: GTNPORTAL-3409 URL: https://issues.jboss.org/browse/GTNPORTAL-3409 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Lucas Ponce Assignee: Lucas Ponce GateIn produces XHTML 1.0 Strict type documents. There are some legacy html elements (i.e. target="_blank") not compatible with XHTML 1.0 Strict type document creating a non compliant markup. -- 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

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues March 2014