Skip to content
This repository has been archived by the owner on May 2, 2024. It is now read-only.

Screen sharing problem with aad user #278

Open
idaaas22 opened this issue Jun 29, 2023 · 4 comments
Open

Screen sharing problem with aad user #278

idaaas22 opened this issue Jun 29, 2023 · 4 comments

Comments

@idaaas22
Copy link

Hello all,

For tests, I have deployed a new ubuntu 23.04 with AAD and Firefox.
During my tests, I have tried to create a meeting to share a screen with firefox.
On the test machine, if I use an aad user, I can't share the screen (feature seems to be blocked). The windows which allow what I want to share never appear.
On the same machine, if I create a local user and do the same things, I can share the screen, all features are OK.

If I check the difference between the 2 accounts, the local account is member of users group but not the aad user.
I have added aad user to users group but it the same result. It don't work.

Do you have an idear about this problem ?

Regards

@denisonbarbosa
Copy link
Member

Hey @idaaas22, thanks for reporting the issue! Would you mind checking if you enabled the mkhomedir PAM module, as shown in our README? Firefox stores some of its configuration values in the home directory, so if you don't have it, it might affect its functionalities.

If you do have the home directory, then would you mind following our Troubleshoot guide and providing some logs so that we can have a better understanding of what could be happening?

@idaaas22
Copy link
Author

Hello and thank you for your quick answer.
So, in my configuration, home directory is enabled with full email address (I have tried with only firstname.lastname but it was the same result).
I have enabled debug mode in aad and nss but I don't see an error in journalctl about aad and nss.
The only error I can see is about firefox and xdg-desktop-portal-gnome.
The command systemctl --user --type=service show me that xdg-desktop-portal-gnome.service + xdg-desktop-portal-gtk.service + xdg-desktop-portal.service are loaded but failed. If I use the same command on a local account, all services are OK.
If I try to start these services, I have a timeout but I don't have the reason yet.

@idaaas22
Copy link
Author

idaaas22 commented Jun 30, 2023

After several tests, problems seems to be linked to xdg-desktop-portal-gnome on ubuntu 23.04
I have tried to switch between gdm3 to lightdm and it work correctly. I can share screens.
There is a bug with version 44. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2013116.
This bug seems to be corrected by ubuntu 23.10. I 'll make new tests.
But I can't explain why it fail only with aad user and it work with local user.

@idaaas22
Copy link
Author

idaaas22 commented Jul 3, 2023

Hello,
To resume all my tests:

  • lightdm : I can login with an aad account but if the session is locked, i'm unable to log again. I don't know if it a locale problem or keyboard mapping. Lightdm, don't show "user is not listed" to insert the new login. => In my case, lightdm is not a solution
  • I don't find any logs which explain were is the problem. I just can see the xdg-desktop-portal-gnome.service don't start.
    For me, the best choice is to switch wayland to X11. You can do it when you have inserted your login name (use the wheel in bottom right to switch from ubuntu to ubuntu Xorg) or by changing options in /etc/gdm3/custom.conf
    If someone else can make tests , maybe we can have more explains.

JOT85 added a commit to JOT85/aad-auth that referenced this issue Apr 23, 2024
aad-auth assigns users to UIDs which are too large for some common software.

There are many reports of this problem, notably relating to
xdg-desktop-portal-gnome not working:

- In ubuntu#278, screensharing does not work
  because the portal is not loaded.
  - We have also had this problem.
- In ubuntu#200, applications take
  excessively long to open.
  - We have experienced this issue with a variety of apps, including the
    nmapplet, gnome-terminal, and chromium.
- In ubuntu#441 brings up exactly this issue,
  but hasn't had a response.

Adding a `min_uid` and `max_uid` configuration option allows the user to specify
the range in which UIDs should be generated, thereby enabling admins to cap the
UIDs at a range which works with most software.

To prevent existing installations from changing their behaviour, the default
values, when the parameters aren't specified in the configuration file, remain
at `100000` and `math.MaxUint32`, however the config template now explicitly
sets the values to values which play nicely with xdg-desktop-portal-gnome, in an
attempt to give new users a better experience.

Also, when a collision is found, instead of only incrementing the UID, which may
overflow and end up as UID 0 (root!!!), we instead wrap around only within the
specified range.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants