March 2014 - gatein-issues - Jboss List Archives

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

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.pl... ] Trong Tran reassigned GTNPORTAL-3414: ------------------------------------- Assignee: Trong Tran (was: Tuyen Nguyen The) > 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: Trong Tran > Attachments: linkedin-registration.png > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > 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, 8 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 Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3414?page=com.atlassian.jira.pl... ] Work on GTNPORTAL-3414 started by Trong Tran. > 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: Trong Tran > Attachments: linkedin-registration.png > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > 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, 8 months

1
0
0 / 0

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

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3415: ---------------------------------- Original Estimate: 0 minutes (was: 3 hours) Remaining Estimate: 0 minutes (was: 3 hours) > 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 > Assignee: Peter Palaga > Fix For: 3.8.0.Final > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3419) Update GateIn to WSRP 2.2.12.Final

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3419?page=com.atlassian.jira.pl... ] Peter Palaga resolved GTNPORTAL-3419. ------------------------------------- Fix Version/s: 3.8.0.Final Resolution: Done > Update GateIn to WSRP 2.2.12.Final > ---------------------------------- > > Key: GTNPORTAL-3419 > URL: https://issues.jboss.org/browse/GTNPORTAL-3419 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Peter Palaga > Fix For: 3.8.0.Final > > > WSRP was released, so, an update on GateIn is required. -- 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-3420) Compose Page API

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3420?page=com.atlassian.jira.pl... ] Juraci Paixão Kröhling updated GTNPORTAL-3420: ---------------------------------------------- Git Pull Request: https://github.com/gatein/gatein-api-java/pull/9 (was: https://github.com/jpkrohling/gatein-api-java/compare/BZ1043858-ComposeAPI) > Compose Page API > ---------------- > > Key: GTNPORTAL-3420 > URL: https://issues.jboss.org/browse/GTNPORTAL-3420 > 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 > > https://community.jboss.org/wiki/RFC-APIForComposingPages -- 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-3420) Compose Page API

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3420?page=com.atlassian.jira.pl... ] Juraci Paixão Kröhling updated GTNPORTAL-3420: ---------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jpkrohling/gatein-api-java/compare/BZ1043858-ComposeAPI > Compose Page API > ---------------- > > Key: GTNPORTAL-3420 > URL: https://issues.jboss.org/browse/GTNPORTAL-3420 > 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 > > https://community.jboss.org/wiki/RFC-APIForComposingPages -- 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-3420) Compose Page API

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3420?page=com.atlassian.jira.pl... ] Juraci Paixão Kröhling commented on GTNPORTAL-3420: --------------------------------------------------- Quickstart: https://github.com/jpkrohling/jboss-portal-quickstarts/compare/GTNPORTAL-... GateIn Portal: https://github.com/jpkrohling/gatein-portal/compare/BZ1043858-ComposeAPI GateIn API: https://github.com/jpkrohling/gatein-api-java/compare/BZ1043858-ComposeAPI > Compose Page API > ---------------- > > Key: GTNPORTAL-3420 > URL: https://issues.jboss.org/browse/GTNPORTAL-3420 > 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 > > https://community.jboss.org/wiki/RFC-APIForComposingPages -- 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-3421) Parameter to externalize jcr values of workspace gets confusing.

by Tran Trung Thanh (JIRA)

Tran Trung Thanh created GTNPORTAL-3421: ------------------------------------------- Summary: Parameter to externalize jcr values of workspace gets confusing. Key: GTNPORTAL-3421 URL: https://issues.jboss.org/browse/GTNPORTAL-3421 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 3.5.8.Final Reporter: Tran Trung Thanh Priority: Minor As far as I know, [gatein.jcr.storage.enabled|https://github.com/gatein/gatein-portal/blob/3...] is used to externalize jcr values of workspace. If it is true, jcr values will be stored in filesystem. On the other hand, jcr value can be found in database. But its name makes customer confusing. They might think that if this parameter is false, it means no storage for jcr data. It should be *gatein.jcr.binaries.filesystem.enable* or *gatein.jcr.values.externalization.enable* -- 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-3420) Compose Page API

by Juraci Paixão Kröhling (JIRA)

Juraci Paixão Kröhling created GTNPORTAL-3420: ------------------------------------------------- Summary: Compose Page API Key: GTNPORTAL-3420 URL: https://issues.jboss.org/browse/GTNPORTAL-3420 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 https://community.jboss.org/wiki/RFC-APIForComposingPages -- 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-3419) Update GateIn to WSRP 2.2.12.Final

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3419?page=com.atlassian.jira.pl... ] Juraci Paixão Kröhling reopened GTNPORTAL-3419: ----------------------------------------------- Wrongly marked as "Resolved", but should be done by Peter (as he's merging it) > Update GateIn to WSRP 2.2.12.Final > ---------------------------------- > > Key: GTNPORTAL-3419 > URL: https://issues.jboss.org/browse/GTNPORTAL-3419 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > > WSRP was released, so, an update on GateIn is required. -- 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