example/plugins//$filename, example: disco_srv: " Remember to edit and customize all the values like "CHANGE_ME!" in the configuration files, in proxy_conf.yaml and in plugins configurations.example/proxy_conf.yml, example: UNKNOW_ERROR_REDIRECT_PAGE: ".To get redirection to these pages, or redirection to third-party services, consider the following configuration files: You can find these demo pages in example/static and edit at your taste. With the help of an additional webserver dedicated for static contents: Discovery Service page The example project comes with the following demo pages, served Discovery Service, interface that allows users to select the authentication endpoint.TargetRouting, a SATOSA microservice for selecting the output backend to reach the endpoint (IdP) selected by the user.Backend, interface of the proxy that is configured as a SAML2 Service Provider.Frontend, interface of the proxy that is configured as a SAML2 Identity Provider.Limitations, traditionally could not interact each other. To adapt and allows to communicate systems that, due to protocol or specific More generally this solution allows us to adopt multiple proxy frontends and backends Spid Identity Providers adapting Metadata and AuthnRequest operations to the Spid technical requirements.įigure1 : Common scenario, a traditional SAML2 Service Provider (SP) that's proxied through the SATOSA SPID Backend gets compliances on AuthnRequest and Metadata operations. Specifically it allows traditional Saml2 Service Providers to communicate with Satosa-Saml2 Spid is an intermediary between many SAML2/OIDC Service Providers (RP) and many SAML2 Identity Providers. eIDAS FICEP SP (see ficep support PR here).That aims to setup a SAML-to-SAML Proxy and OIDC-to-SAML compatible with the SPID - the Italian Digital Identity System. This is a SAML2/OIDC configuration for SATOSA
0 kommentar(er)
