Relation between CompliSpace IdP Tool, CompliSpace App and Client IdP

What is the nature of this tool, is it functioning as an IdP or SP beyond the end user's web browser?

In essence the CompliSpce IdP tool is acting as both:

1. Each CompliSpace app acts as an SP which will be configured to use the CompliSpace IdP for authentication.
2. CompliSpace IdP will then act in a proxy role as an SP and pass on authentication requests to the client IdP
3. The client IdP will authenticate the user and provide the usual SAML attributes.
4. CompliSpace IdP will then validate the SAML details, including the requested SP and allowed site for the user and provide authentication back to the CompliSpace SP

This technical diagram shows a general overview of how the CompliSpace IdP Tool functions as both IdP and SP.

While this diagram shows an example of the CompliSpace IdP acting as a Federated IdP (Proxy) to connect the SSO service to our product suite (OAuth protocol example).