Tags: azjezz/connect
Tags
Merge pull request symfonycorp#53 from sensiolabs/oauth-exception Add a flag to catch oAuth Exception
feature symfonycorp#50 [RFR] Use user's roles if user is an instance … …of UserInterface instead of token's roles (iamluc) This PR was merged into the 4.x-dev branch. Discussion ---------- [RFR] Use user's roles if user is an instance of UserInterface instead of token's roles Commits ------- b83f3ac Use user's roles if user is an instance of UserInterface instead of token's roles
feature symfonycorp#47 Improved OAuth errors handling (tucksaun) This PR was squashed before being merged into the 3.x-dev branch (closes symfonycorp#47). Discussion ---------- Improved OAuth errors handling As discussed @lyrixx, we now rely on the `DefaultAuthenticationFailureHandler` of Symfony which handles redirection in a clean way and as our work in `ConnectAuthenticationFailureHandler` is already handled in `AbstractAuthenticationListener` which is already extended by `ConnectAuthenticationListener` To be able to do that we need to make `OAuthException` extends `AuthenticationException` Commits ------- 51fbc5b Improved OAuth errors handling
minor symfonycorp#44 [RFR] Fixed Serialization of AbstractEntity (tuc… …ksaun) This PR was merged into the 2.x-dev branch. Discussion ---------- [RFR] Fixed Serialization of AbstractEntity Currently the serialisation of `ConnectToken` trigger the serialisation of `ApiUser`. However the serialisation of `ApiUser` is naive and nothing in particular is done. This leads to a really big string (~500 Kb in my case) and can lead to potential break (in my case only in production :/) because of the serialisation of `SensioLabs\Connect\Api\Api`. Moreover there is no advantage of serialising it as it's not usable afterwards (see symfonycorp#15). Commits ------- 9dd6e1e Fixed Serialization of AbstractEntity
PreviousNext