-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue: First time login through Bastion fails #592
Comments
A big more info, I didnt have the debug info set quite right but now I do and here's more info about what happens when I try to login using authd from an Azure Bastion host
So, it looks like its failing because I cant respsond to the broker selection. Is there a way to force it default to EntraId? |
It seems your PAM client doesn't handle the PAM conversation properly... In particular |
Ok so such client does not support the PAM_PROMPT_ECHO_ON conversations, so those where the input is shown to the user. As workaround, maybe, we may just always use |
OK, the issue is with xrdp not handling the PAM_PROMPT_ECHO_ON at all. A possible workaround could be implemented from the authd side but the better solution is for srdp to handle the message and interaction. Thanks for looking into this! I'll submit a feature request to the xrdp project. |
Ok, looks like xrdp isn't going update any time soon with this functionality :( . Any chance for the Authd workaround to be done? |
Well it's still a bit problematic because I feel that even doing it, xrdp wouldn't support multiple requests... |
Is there an existing issue for this?
Describe the issue
After setting up authd and the EntraID broker, new users cannot login for the first time via Azure Bastion via SSH or RDP
Steps to reproduce
1 Create Ubuntu 24.04 VM on Azure
2. Setup Authd and EntraID broker per dcoumentation wiki.
3. Attempt to login to VM via AzureBastion host.
4. Login will fail
From different VM on same network, attempt SSH to new VM. Login will succeed.
At this point, the RDP or SSH Bastion login will also work.
System information and logs
authd version
authd-msentraid broker version
gnome-shell version
Distribution
Logs
authd broker configuration
/etc/authd/brokers.d/msentraid.conf
authd-msentraid configuration
Double check your logs
The text was updated successfully, but these errors were encountered: