Giuseppe De Marco

Abandon cookie as session storage for v2.0.0

16

Due to the latest cookie restrictions made by modern web browser, eg: samesite cookie, I'm wondering if it were time to rewrite entirely the session backend used to store SAML2...

Recently we added support for SAML2 Scoping but this is still uncovered by tests. see: https://github.com/IdentityPython/djangosaml2/blob/86a5dc792e29e873714b18600f17e0d7b7e8d657/djangosaml2/views.py#L195 @pauldekkers ^

(TLS negotiation failure) when connecting to ldaps://fqdn:636 server

3

Using `ldap-merger.tac` I cannot connect to ldaps port 636. No problem to port 389 with or without start TLS. Tracelog here: ```` 2019-07-19T01:27:42+0200 [twisted.internet.defer#critical] Unhandled error in Deferred: 2019-07-19T01:27:42+0200 [twisted.internet.defer#critical]...

feat: cookie parameters in proxy configuration

2

This PR fixes https://github.com/IdentityPython/SATOSA/issues/344 introducing the following paramenters to be optionally handled in the proxy global configuration. **Secure** Now can be disabled via `COOKIE_SECURE: no` in proxy_conf.yaml. Default: True that's...

HTTP Redirect page on UnknowError Exception

1

This PR introduces a new proxy_config.yml parameter called UNKNOW_ERROR_REDIRECT_PAGE, a possibility to redirect to that page all the Users that gets UnknowError Exception in the Http Response. - Added a...

Context state keyError Exception message for humans

2

This PR introduces a human readable message to Users when they gets SATOSA_BASE KeyError. Found it usefull to avoid weird Users open assistane tickets when they gets that "ermetic" error...

I could be wrong, so forgive me eventually! Using Saml2Saml I found that SATOSA does not check the consistency between `in_response_to` and the identifier of the original Authn Request. Specifically,...

As we can see all these parameters are costant in the code. Better to manage them as configurable variables 

[Debug enhancement] IncorrectlySigned exception on AuthnRequest when MDQ server is down

1

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...