[
https://issues.apache.org/jira/browse/SHINDIG-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik BI updated SHINDIG-1863:
-----------------------------
Summary: Shindig should Container to force the st on all gadget requests
and to be refreshed due to a change it knows about (was: Shindig should
provide api so client side can force the st to be refreshed )
> Shindig should Container to force the st on all gadget requests and to be
> refreshed due to a change it knows about
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SHINDIG-1863
> URL: https://issues.apache.org/jira/browse/SHINDIG-1863
> Project: Shindig
> Issue Type: Bug
> Components: Java, Javascript
> Affects Versions: 2.5.0
> Reporter: Erik BI
>
> We have uncovered several use cases request that:
> 1. Container's abilty to require a ST for all gadgets and cause it to refresh
> 2. Container determines that all STs are invalid (e.g. the user logged out,
> SSO session times out, etc) ... should be able to force an immediate refresh
> to reflect the new log in state. where the container wants to force the use
> of STs on all requests.
> However, there is no API in the container can call to force a refresh of all
> STs due to a change it knows about (change of logged in user) and if the
> gadget does not request the "auth-refresh" indirectly, shindig will not
> refresh its token.
> related java code:
> Boolean needsTokenRefresh =
> isFieldIncluded(fields, "needstokenrefresh") ?
> gadget.getAllFeatures().contains("auth-refresh") : null;
--
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
