Giuseppe De Marco

in this place: https://github.com/IdentityPython/SATOSA/blob/master/src/satosa/base.py#L89 we could pass proxy config as argument or, better, call in the MS constructor a global function that does the following actions before returning satosa_config: config_file...

Hi guys, I think that we should implement our ideas following the goals related to these. Code style and patterns are very important but they shouldn't block the availability of...

> Travis is fine with py3.6, 3.7 and 3.8. Only py3.5 is failing - it should be removed. Important decision. Ubnt 16.04 and debian9 still have py35 as default

> > Travis is fine with py3.6, 3.7 and 3.8. Only py3.5 is failing - it should be removed. > > Can you explain why this error exists only in...

Bytheway removing py35 could be done in a future release, I think that 2021 should be the year to abadon py35

Hi scott, long time I don't use anymore satosa's ldap_attr_store but I faced what you're telling us. I'm using pyMultiLdap and it come with a satosa ms, here: https://github.com/peppelinux/pyMultiLDAP/blob/master/multildap/satosa/multiple_ldap_attribute_store.yaml.example https://github.com/peppelinux/pyMultiLDAP/blob/master/multildap/satosa/multiple_ldap_attribute_store.py...

This issue is related to pysaml2 mdstore and not directly to SATOSA but it could be handled in a better way instead of expose an error 500 if you agree

Wouldn't it be Better to merge all this issues to a single topic regarding the exception handling and representation to users? Probably this Is also related to https://github.com/IdentityPython/SATOSA/pull/221 What do...

@skoranda take a look bere https://github.com/IdentityPython/SATOSA/pull/240 This makes client connection strategies be configurable via microservice yaml definitions. With a client_strategy = ldap3.RESTARTABLE this problem Will be solved I think

Hi @skoranda is this ready to be closed or the problem still persist?