It's hard to demonstrate the issues that SAML and Higher Ed will hit with FedCM to the W3C participants and browser teams without actual demonstrations. Testing enables visceral contribution back on how the APIs function for all parties.

Testing advice

Network actions Because there is no browser provided insight to browser actions related to the FedCM API callsthe advice is to use an application such as Fiddler, Charles Proxy, Burp suite, Proxy Man  etc.  ProxyMan handles the SSL handling for you relatively easily and is free.

Issues with testing

The "developer tools" fails to show any information about the browser's actions in response to the API calls. Despite requests to our browser contacts, there is no movement here.

  • No labels