Workflow is following:
- app-A - registers frontchannel_logout_uri_1
- app-B - registers frontchannel_logout_uri_2
- app-A - login to AS
- app-B - login to AS (SSO)
- app-A - calls /end_session
- AS - returns back HTML with iframes where each iframe points to all frontchannel_logout_uris within this session, in our case it is `frontchannel_logout_uri_1` and `frontchannel_logout_uri_2`
- browser load HTML (with all iframes means that it calls `frontchannel_logout_uri_1` and `frontchannel_logout_uri_2`)
app-A does not know anything about `frontchannel_logout_uri_2`, it just calls `/end_session` endpoint and it's responsibility of AS to track it and return correct HTML page with iframes (once iframe is loaded, it means that `frontchannel_logout_uri_2` is called and app-B must log itself out).
I hope it is more clear now.
Thanks,
Yuriy