SATOSA
SATOSA copied to clipboard
Proxy translating between different authentication protocols (SAML2, OpenID Connect and OAuth2)
When we use a SAML backend with metadata from mdq server and the mdq server is unavailable, SATOSA raises a UnkownError. In the debug log we can read the exception...
In the current Documentation we have `attribute_profile` option [as a string argument](https://github.com/IdentityPython/SATOSA/blame/master/doc/README.md#L150), for mapping attributes from/to response. Can we have an example configuration to use this option? Otherwise I'll have...
From a deployer: "the satosa 500 error continues - it seems to start each night when the ldap server reboots & scales down. rebuilding the satosa stack fixes it"
With SaToSa SAML frontend configured with edugain metadata, every request takes several minutes to serve. It seems like the plugin is parsing the metadata on every request, because the delay...
Is there any possibility to implement, in the SAML2 backend and frontend plugins, the SLO endpoint?
If an exception is well understood and reported, there is no point in adding a stacktrace. E.g.: currently a saml2.s_utils.UnknownSystemEntity exception will result in a stacktrace (and disguise it as...
- We have configured Keycloak Client as the Oauth Client(Requests as OpenId-connect)(frontend) - We are using Facebook as the Oauth Server(Responds as Oauth)(backend) - Trying to use SATOSA as a...
The SAML2 SP backend should check the scope on scoped attributes asserted by an authenticating IdP and compare with the scope from the SAML metadata for the authenticating IdP and...
Decouple base oauth2 plugin from facebook and leave this in core satosa
misleading exception if condition mentioned in title occurs ## Code Version 4.4.0 ## Expected Behavior exception should name the correct cause ## Possible Solution (1) rename exception to "unkown Entity...