Phone samples show the rstr from wsfedp being stored in per app phone memory.
Should the embedded swt expire (making it useless as a http bearer header for passing guards on some api endpoint), the idea is that one can reffesh - presumably without user challenge.
Does one use ws trust (active) endpoints of acs to refresh the "response" from a wsfedp PASSIVE run?
