On 31.3.2015 10:16, Sebastian Rose wrote:
> That's actually related to the application session (kind of
HttpSession
> ID in web application secured by keycloak). We can add support for
> changing application_session_state in refreshToken endpoint instead of
> introducing separate endpoint. Will it be sufficient for your usecase?
> Marek
As Bastian already said...
Thanks for your response. Yes, i think this would work for us.
I will create a JIRA for that and contribute a change via pull request (if this is fine
for you)?
yep, thanks. There is some refactoring in latest master, you would need
to look at TokenEndpoint.buildRefreshToken now (TokenEndpoint is new
class, which didn't exist in 1.1.0.Final)
Marek
Best regards,
Sebastian