Add email attribute to GenericUser

[andreboscatto]

• Adding email attribute to GenericUser;
• Keeping mail and email (retro-compatibility) for LDAP tests while we standardize it. I'll open a new PR to remove the mail and keep it there to be merged after we deal with sssd tests.

[andreboscatto]

• Need help to clean this branch from previous changes
• Need to understand how to test the changes I made (I was unable to do it locally)
• Need to validate if the attributes I changed are the right ones (specially for IPA which didn't have the email attribute before)

[danlavu]

• Need to understand how to test the changes I made (I was unable to do it locally)

cd ~/git/sssd_repository
pip uninstall sssd_test_framework
pip install -e ~/path/to/sssd_test_framework

-e = editable

Now you should be able to change the test code and have the attribute available to you.

[madhuriupadhye]

• Need to understand how to test the changes I made (I was unable to do it locally)

cd ~/git/sssd_repository
pip uninstall sssd_test_framework
pip install -e ~/path/to/sssd_test_framework

-e = editable

Now you should be able to change the test code and have the attribute available to you.

You can also verify using git commit hash,
for ex,

(.venv) mupadhye@mupadhye-thinkpadp1gen4i:~/working/sssd/src/tests/system$ pip freeze | grep sssd-test-framework
-e git+ssh://git@github.com/madhuriupadhye/sssd-test-framework.git@8b02c318a37b71ad76367be9f1bac92e45862acc#egg=sssd_test_framework

here is my commit ID,

commit 8b02c318a37b71ad76367be9f1bac92e45862acc (HEAD -> id_override, origin/id_override)
Author: Madhuri Upadhye <mupadhye@redhat.com>
Date:   Tue Mar 4 12:36:40 2025 +0530

    IPA ID Override classes for users and groups

[jakub-vavra-cz]

Hi wouldn't it be better to have email populated by default by username@domain ?
I would switch the logic around to enable not setting up an email but have it there by default.
We can extend authentication tests to use the email afterwards.

[andreboscatto]

Hi @jakub-vavra-cz

I like the idea, but my suggestion is to do it in the "agile" way, with small increments. If this PR is sufficient for the purpose we need now, let's move ahead and merge it.

We can open a new issue/PR implementing your suggestion, wdyt? This way we don't keep this PR open for a long time while we discuss those details and set a final agreement/resolution (my PoV).

[jakub-vavra-cz]

LGTM. We can address default email in the future.

[justin-stephenson]

Ack, thank you.