[Satosa-dev] hasher microservice
29 Nov
2018
29 Nov
'18
11:41 p.m.
On Fri, 30 Nov 2018 at 00:19, Paul Caskey <pcaskey at internet2.edu> wrote:
Thanks, Ivan.
I can only guess that some part of your code (most probably a
microservice) is using this component. Do you have any custom
microservices?
--
Ivan c00kiemon5ter Kanakarakis >:3
microservice. In the form of a microservice it
can now be chosen whether
this should take place or not; and the configuration has been extended to
define if this should take place when a specific SP-entityid is met.
Along with this, some configuration options are no longer needed. One of
them is USER_ID_HASH_SALT. As SATOSA is not performing the hash, it does
not need that configuration option anymore. If there is a reason that you
Removing USER_ID_HASH_SALT from proxy_conf.yaml cleared one of the two hash-related
deprecation warnings I was seeing.
I am still seeing the following and, so far, am not able to track it down:
"/usr/local/lib/python3.6/site-packages/satosa/deprecated.py:173:
DeprecationWarning: UserIdHashType is deprecated and will be removed.
_warnings.warn(msg, DeprecationWarning)"
I don't see that anywhere in my config files...
Any pointers?