[keycloak-dev] KeycloakSecurityContext serialization issue

Marek Posolda mposolda at redhat.com
Tue Apr 21 03:17:00 EDT 2015

That's strange, serialization and deserialization of 
KeycloakSecurityContext should work fine. KeycloakSecurityContext 
actually uses java custom serialization (it implements writeObject and 
readObject methods). So during deserialization it calls readObject and 
creates AccessToken and IDToken from the base64 encoded token. This 
works fine in cluster and we also have the test for it: 

If you still seeing issues and you think that it's bug, feel free to 
create JIRA. But please add the exact steps to reproduce to the JIRA.


On 21.4.2015 00:50, Leonardo Loch Zanivan wrote:
> Hi,
> I'm facing a problem while deserializing KeycloakSecurityContext of a 
> Basic Auth KeycloakAccount.
> KeycloakSecurityContext stores Basic Auth base64 token instead of 
> Access Token, so deserialization code fail!
> *String[] parts = encoded.split("\\."); if (parts.length < 2 || 
> parts.length > 3) throw new IllegalArgumentException("Parsing error");*
> https://github.com/keycloak/keycloak/blob/master/core/src/main/java/org/keycloak/KeycloakSecurityContext.java
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/keycloak-dev/attachments/20150421/3e2c5ab8/attachment.html 

More information about the keycloak-dev mailing list