Denison Barbosa

This is not something that we can show on authd. If you don't have these values configured, the broker service won't even start, so you should take a look at...

Hey, @selcem-artan! Thanks for reporting the issue. Would you mind following the guides listed on the issue template (they can be seen at the issue description right above) to provide...

Hey, @selcem-artan. The `adsysctl service cat` command is a monitoring command, i.e. you need to run it and then run another adsysctl command in a separate terminal. However, running `adsysctl...

As we talked about privately, I will close this issue since this is not a bug. The user wants to rely on [loopback processing](https://learn.microsoft.com/en-us/troubleshoot/windows-server/group-policy/loopback-processing-of-group-policy) to apply user policies and this...

@3v1n0, can we close this one and come back to it later? Considering the whole SRU situation, it's gonna take a while before we get Go 1.24 in Noble, so...

Hey, @mwilcher-gp! Thanks for reporting this issue. Sadly, the logs are a little bit incomplete. The error: `level=ERROR msg="could not create broker with provided issuer and client ...` (there's more...

I was talking about `/var/snap/authd-msentraid/current/broker.conf`. If everything looks ok in the file, can you paste the entire error message (the one I mentioned that's incomplete)?

Yes, those are the only required lines for the broker to work. The `home_base_dir` and `ssh_allowed_suffixes` are optional values.

Thanks for reporting back! It seems like the broker can't find your provider. Can you take a look at https://github.com/ubuntu/authd/wiki/03---Configuration#entra-id-configuration and make sure everything is configured as it should?

This one is tricky. We can't know for sure why we failed to reach the provider. Since we provide a template for the broker configuration, we always have at least...