You also acknowledge that your account is personal to you and agree not to provide any other person with access to the Services or portions of it using your user name, password, or other security information. If you choose, or are provided with, a user name, password, or any other piece of information, as part of our security procedures, you must treat such information as confidential, and you must not disclose it to any other person or entity. Please note, you are responsible for keeping your login credentials secret at all times, including your username and password.
In other instances, such as when we use cookies or contact you about our Services, we will determine the means and purpose of processing.Īlthough we maintain the controls listed herein, transmission of data is not without risk and we complete security of your personal data cannot be guaranteed. For purposes of the EU GDPR, the Customer is considered a data controller in these respects and we are a data processor. In conducting these activities, the Customer maintains control over what personal data is collected, how it is used, how long it is retained, and who it is disclosed to. Our Customers use our Services to post job opportunities, evaluate job applicants, manage their human resource activities, and train their workforce. When configuring username/password on the URI statically, then a StaticCredentialsProvider holds the configured information. Credentials are obtained at connection time from RedisCredentialsProvider. Connections are authenticated by using the information provided through RedisCredentials. Redis URIs may contain authentication details that effectively lead to usernames with passwords, password-only, or no authentication. You have following possibilities to create a RedisURI: The unified form is RedisURI.You can provide the database, password and timeouts within theRedisURI.
Connections to a Redis Standalone, Sentinel, or Cluster require aspecification of the connection details.
0 kommentar(er)
