Can you elaborate on what exactly the issue is? I'm don't understand what you are doing. Are you manually invoking the token endpoint to exchange authorization code for access token? If so that should work just fine with Jackson 2 (fasterxml) as that's what our adapters do (and we have plenty of tests that do this).

On 9 March 2016 at 19:50, Lohitha Chiranjeewa <kalc04@gmail.com> wrote:

Yes, we have upgraded the adapters as well.

Seems the new Jackson version doesn't accept the @JsonProperty annotation against each variable itself, but they should be placed against getters and setters instead?

 

On Wed, Mar 9, 2016 at 5:31 PM, Stian Thorgersen <sthorger@redhat.com> wrote:

On 9 March 2016 at 12:45, Lohitha Chiranjeewa <kalc04@gmail.com> wrote:

Hi,

When we were testing out 1.9.0.Final, we came across two issues:

1) NullPointerException during DB migration (from 1.7.0 to 1.9.0) because of an issue in org.keycloak.migration.migrators.MigrateTo1_9_0.java class. Basically if realm.getDisplayNameHtml() is null, the exception gets thrown.

Fixed

 

2) Cannot map the access codes returned after authentication to the AccessTokenResponse.java class. A jsonifying error occurs. Seems this has something to do with @JsonProperty annotation that has impacted with Jackson version upgrade.

Did you upgrade adapters as well as the server?

 

Are these issue already tracked? If not I can create JIRAs.

Regards,

Lohitha.

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user