Mindful auth

[Diego-H-S]

Summary

Mindful API has undergone a change in its structure. Since three weeks ago we are not able to access the API by adding credentials in the header. The solution given by the HCL support team is using auth parameter in the request function, and it was implemented in the present PR.

On the other hand, Instead of Bearer authentication, a new Basic authentication is used. The client chose this new way of authentication to avoid future problems with archived credentials after 90 days.

Importance

Required by client. Very important.

Checklist

This PR:

• follows the guidelines laid out in CONTRIBUTING.md
• links relevant issue(s)
• adds/updates tests (if appropriate)
• adds/updates docstrings (if appropriate)
• adds an entry in CHANGELOG.md

[Rafalz13]

Please modify tests for Mindful source and task if needed.

[Rafalz13]

Here you are getting CUSTOMER_UUID and AUTH_TOKEN but docstring in the source says that The structure is user and password. What is correct?

[Diego-H-S]

In mindful, the user is defined by an ID, in this case, CUSTOMER_UUID, and the password is defined by, what they said AUTH TOKEN, but this is a password, I mean, if you need to generate a token for OAuth, this not would be correct, you would have to create a token.

[Diego-H-S]

when I saved it to the credentials, I added the same words they decided to use for the user (mindful velux user) and the password (mindful velux password).

[Rafalz13]

The docstring says that The structure is user and password. In the task, you are getting CUSTOMER_UUID and AUTH_TOKEN. It doesn't look like a username and password.

[Diego-H-S]

But the auth accepts the function HTTPBasicAuth which only needs the user and password.
I you think it necessary for name consistency, I could replace user and password in docstring by customer_uuid and auth_token respectively.