[SHINDIG-1863] Shindig should support Container to force the st on all gadget requests and to be refreshed due to a change it knows about

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 2.5.0, 2.5.0-beta6
• Component/s: Java, Javascript
• Assignee: Unassigned
• Reporter: Erik BI
• Created: 29/Aug/12 05:55
• Updated: 14/Aug/13 11:32
• Resolved: 14/Jan/13 15:39

Description

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;

Issue Links

• is blocked by: SHINDIG-1924 Common container mechanisms to support refreshing all gadget tokens have JavaScript errors
• is blocked by: SHINDIG-1929 CLONE - Common container mechanisms to support refreshing all gadget tokens have JavaScript errors