客户端获取配置的加密算法存在弱加密算法，存在安全风险

Hello, the signature algorithm for the interface used by the client to retrieve configuration is currently HmacSHA1, which is a weak encryption algorithm. The interface itself is part of the microservice configuration pull, and there may be sensitive configurations, which may pose security risks with the weak encryption algorithm. At the same time, we also consider compatibility issues. We do not know whether it is possible to support allowing simultaneous verification of HmacSHA1 or HmacSHA256, with HmacSHA1 being preferred, and if decryption fails, HmacSHA256 verification can be used again to improve the weak encryption algorithm on the client side. At the same time, is it possible to record some records of verification using HmacSHA1, which will facilitate the upgrade of clients using the weak encryption algorithm?