March 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3416) UI error message instead of HTTP400 when trying to impersonate twice

by Vlastislav Ramik (JIRA)

Vlastislav Ramik created GTNPORTAL-3416: ------------------------------------------- Summary: UI error message instead of HTTP400 when trying to impersonate twice Key: GTNPORTAL-3416 URL: https://issues.jboss.org/browse/GTNPORTAL-3416 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: 3.8.0.Beta01-SNAPSHOT Reporter: Vlastislav Ramik Assignee: Marek Posolda Steps to reproduce: 1. sign in as a root 2. go to users and group management 3. impersonate root user 4. go to users and group management 5. try to impersonate user actual results: HTTP400 + ERROR message in log expected results: UI error message (not sure what about ERROR message in log) -- 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, 9 months

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 reassigned GTNPORTAL-3404: ------------------------------------- Assignee: Tuyen Nguyen The > 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 > Assignee: Tuyen Nguyen The > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-374) Improve admin GUI to be W3C compliant

by Lucas Ponce (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-374?page=com.atlassian.jira.plugi... ] Lucas Ponce updated GTNWSRP-374: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-wsrp/pull/92 > Improve admin GUI to be W3C compliant > ------------------------------------- > > Key: GTNWSRP-374 > URL: https://issues.jboss.org/browse/GTNWSRP-374 > Project: GateIn WSRP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Admin GUI > Affects Versions: 2.2.11.Final > Reporter: Lucas Ponce > Assignee: Juraci Paixão Kröhling > Fix For: 2.2.12.Final > > > Admin GUI portlet has some issues incompatible with XHTML 1.0 spec: > - <link> tags rendered inside <body> tags. > - Repeated id attributes in generated JSF tags. > - Other minor enhancenemtns. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-374) Improve admin GUI to be W3C compliant

by Lucas Ponce (JIRA)

Lucas Ponce created GTNWSRP-374: ----------------------------------- Summary: Improve admin GUI to be W3C compliant Key: GTNWSRP-374 URL: https://issues.jboss.org/browse/GTNWSRP-374 Project: GateIn WSRP Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Admin GUI Affects Versions: 2.2.11.Final Reporter: Lucas Ponce Assignee: Juraci Paixão Kröhling Fix For: 2.2.12.Final Admin GUI portlet has some issues incompatible with XHTML 1.0 spec: - <link> tags rendered inside <body> tags. - Repeated id attributes in generated JSF tags. - Other minor enhancenemtns. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3414) Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension

by Tuyen Nguyen The (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.pl... ] Tuyen Nguyen The updated GTNPORTAL-3414: ---------------------------------------- Git Pull Request: https://github.com/gatein/gatein-portal/pull/799 > Oauth improvement: enable developer change the way to generate gatein user for each oauth provider via extension > ---------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3414 > URL: https://issues.jboss.org/browse/GTNPORTAL-3414 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > Attachments: linkedin-registration.png > > > When i register new account with LinkedIn, i see a registration form with random-string username prefilled (see attachment) > It's because LinkedIn does not provide username as unique attribute for each user, so we have to get userid instead of username, and this is a random-string by LinkedIn > Now, We can improvement method OAuthUtils#convertOAuthPrincipalToGateInUser() and customize the way to convert oauth-principal to gatein user for linkedIn. > But when someone provide other oauth integration via extension, he can not customize OAuthUtils#convertOAuthPrincipalToGateInUser() method to generate gatein user by the way that oauth should do. > So we should enable developer change the way to generate gatein user for each oauth provider via extension. > To enable developer change the way to generate gatein user via extension, we will: > - Introduce OAuthUserGenerator service and it can add OAuthUserGeneratorPlugin by extension. This service will response to generate gatein user from oauth-principal > - Method OAuthUserGenerator#generateGateInUser(OAuthPrincipal principal) will do: > + Find OAuthUserGeneratorPlugin by oauthProviderType, > + If found plugin for this oauth provider it will delegate method OAuthUserGeneratorPlugin#generateGateInUser() > + If not found, it will delegate to OAuthUtils#convertOAuthPrincipalToGateInUser() as default. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-373) Empty producer-handler-chains causes WARN

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-373?page=com.atlassian.jira.plugi... ] Juraci Paixão Kröhling updated GTNWSRP-373: ------------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged. > Empty producer-handler-chains causes WARN > ------------------------------------------ > > Key: GTNWSRP-373 > URL: https://issues.jboss.org/browse/GTNWSRP-373 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > > We make use of a @HandlerChain , pointing to a file which contains no handler chains, just the top-level element <handler-chains>. For pre-EAP 6.2, it was not a problem, but on EAP 6.2 and on, a WARN is shown on the log during deployment (or boot, as this is part of an extension). > {{WARN org.jboss.as.webservices JBAS015602: Invalid handler chain file: handler-chain.xml}} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-373) Empty producer-handler-chains causes WARN

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-373?page=com.atlassian.jira.plugi... ] Juraci Paixão Kröhling updated GTNWSRP-373: ------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-wsrp/pull/91 > Empty producer-handler-chains causes WARN > ------------------------------------------ > > Key: GTNWSRP-373 > URL: https://issues.jboss.org/browse/GTNWSRP-373 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > > We make use of a @HandlerChain , pointing to a file which contains no handler chains, just the top-level element <handler-chains>. For pre-EAP 6.2, it was not a problem, but on EAP 6.2 and on, a WARN is shown on the log during deployment (or boot, as this is part of an extension). > {{WARN org.jboss.as.webservices JBAS015602: Invalid handler chain file: handler-chain.xml}} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-373) Empty producer-handler-chains causes WARN

by Juraci Paixão Kröhling (JIRA)

Juraci Paixão Kröhling created GTNWSRP-373: ---------------------------------------------- Summary: Empty producer-handler-chains causes WARN Key: GTNWSRP-373 URL: https://issues.jboss.org/browse/GTNWSRP-373 Project: GateIn WSRP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Juraci Paixão Kröhling Assignee: Juraci Paixão Kröhling We make use of a @HandlerChain , pointing to a file which contains no handler chains, just the top-level element <handler-chains>. For pre-EAP 6.2, it was not a problem, but on EAP 6.2 and on, a WARN is shown on the log during deployment (or boot, as this is part of an extension). {{WARN org.jboss.as.webservices JBAS015602: Invalid handler chain file: handler-chain.xml}} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler

by Martin Weiler (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.pl... ] Martin Weiler updated GTNPORTAL-3415: ------------------------------------- Git Pull Request: https://github.com/gatein/gatein-portal/pull/798 > URL query parameters are lost in the authentication process with LegacyRequestHandler > ------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3415 > URL: https://issues.jboss.org/browse/GTNPORTAL-3415 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.8.Final > Reporter: Martin Weiler > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Steps to reproduce > - Goto url http://localhost:8080/portal/private/classic/home/restricted?myparameter=... > --> it redirect to login page, login as root --> Query parameters are lost. > Note: Without the LegacyRequestHandler - http://localhost:8080/portal/classic/home/restricted?myparameter=TEST - the parameters are preserved with the fix for GTNPORTAL-3389 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler

by Martin Weiler (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.pl... ] Martin Weiler updated GTNPORTAL-3415: ------------------------------------- Fix Version/s: (was: 3.7.0.Final) (was: 3.5.9.Final) Description: Steps to reproduce - Goto url http://localhost:8080/portal/private/classic/home/restricted?myparameter=... --> it redirect to login page, login as root --> Query parameters are lost. Note: Without the LegacyRequestHandler - http://localhost:8080/portal/classic/home/restricted?myparameter=TEST - the parameters are preserved with the fix for GTNPORTAL-3389 was: Steps to reproduce - Goto url http://localhost:8080/portal/g/:platform:administrators/administration/re... --> it redirect to login page, login as root --> Query parameters are lost. Assignee: (was: Vu Viet Phuong) Git Pull Request: (was: https://github.com/gatein/gatein-portal/pull/779) > URL query parameters are lost in the authentication process with LegacyRequestHandler > ------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3415 > URL: https://issues.jboss.org/browse/GTNPORTAL-3415 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.8.Final > Reporter: Martin Weiler > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Steps to reproduce > - Goto url http://localhost:8080/portal/private/classic/home/restricted?myparameter=... > --> it redirect to login page, login as root --> Query parameters are lost. > Note: Without the LegacyRequestHandler - http://localhost:8080/portal/classic/home/restricted?myparameter=TEST - the parameters are preserved with the fix for GTNPORTAL-3389 -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues March 2014