[Satosa-dev] Fwd: SaToSa for SP 1:n mapping and profile update workflow
31 May
2017
31 May
'17
8:10 a.m.
We have been testing successfully with pyFF for this, and next to that
also use pyff as our mdq. not dealing with metadata files makes satosa
significantly faster.
cheers,
Niels
On 31-05-17 10:03, Scott Koranda wrote:
--
Niels van Dijk Technical Product Manager Trust & Security
Mob: +31 651347657 | Skype: cdr-80 | PGP Key ID: 0xDE7BB2F5
SURFnet BV | PO.Box 19035 | NL-3501 DA Utrecht | The Netherlands
www.surfnet.nl www.openconext.org
(4) Allow
embedded discovery (SHOULD)
I am not sure what you mean by "embedded".
The SAML backend that interfaces with IdPs requires a discovery service
if there is metadata for more than one IdP. Normally you would just
configure that backend with the URL for an existing SAML discovery service.
If you really want SATOSA to "embed" the discovery service you could
write it as another frontend/backend (just inherit from the base classes
as the existing SAML frontend/backend do) with its own URL space.