[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:
----------------------------------------
Attachment: linkedin-registration.png
> 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
[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)
Tuyen Nguyen The created GTNPORTAL-3414:
-------------------------------------------
Summary: 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
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
[JBoss JIRA] (GTNCOMMON-23) Add support for reversing character entities into chars
by Juraci Paixão Kröhling (JIRA)
Juraci Paixão Kröhling created GTNCOMMON-23:
-----------------------------------------------
Summary: Add support for reversing character entities into chars
Key: GTNCOMMON-23
URL: https://issues.jboss.org/browse/GTNCOMMON-23
Project: GateIn Common
Issue Type: Feature Request
Reporter: Juraci Paixão Kröhling
The EntityEncoder currently has means to convert a given input into character entities, meant to be safe for display as HTML. As part of GTNPORTAL-3400, we need a way to do the reverse: get the char for a given character entity.
--
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
[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 commented on GTNPORTAL-3402:
----------------------------------------------------
Juraci Paixao Krohling <jcosta(a)redhat.com> changed the Status of [bug 973835|https://bugzilla.redhat.com/show_bug.cgi?id=973835] from ASSIGNED to POST
> 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
10 years, 9 months