Skip to main content
AUTHENTICATION

Devices keep the logins they have

Sendman accepts LOGIN, PLAIN, NTLM, the mechanisms old hardware actually implements. It checks the password against Microsoft Entra ID or against its own credential vault, so nothing has to be retyped on the device.

  • LOGIN, PLAIN, NTLM
  • Microsoft Entra ID or the Sendman credential vault
  • Vault encrypted with AES-256-GCM

Sendman accepts LOGIN, PLAIN and NTLM

These are the mechanisms scanners, alarm panels and line-of-business applications implement. LOGIN and PLAIN work with Entra ID accounts and with vault credentials. NTLM, which almost nothing else in front of Microsoft 365 still speaks, works with a credential from the vault.

Which mechanism works with which identity source
MechanismEntra ID accountVault credential
LOGIN✓✓
PLAIN✓✓
NTLM—✓

Directory accounts, hybrid logins and devices without a login

  • Entra ID accounts sign in with their own password

    A device that already signs in with a directory account keeps it. Sendman validates the user name and password against Microsoft Entra ID, with no app registration, no consent and nothing to change in your tenant.

  • Multi-factor authentication and Conditional Access

    Multi-factor authentication and Conditional Access do not stand in the way, even with strict policies, and the device never sees a prompt.

  • Hybrid logins such as CONTOSO\svc-scan keep working

    A device set up years ago with a domain login keeps it. Sendman finds the Entra ID account that belongs to the on-premises name, so nobody has to visit the printer. This works with LOGIN and PLAIN for accounts synced from Active Directory.

A vault credential for every device that should not carry a directory identity

Give a device a Sendman credential instead of an account in your directory. It can carry the name the device already uses, CONTOSO\svc-scan included, so the device setup stays as it is.

  • Passwords are encrypted with AES-256-GCM, compared in constant time and never shown again after you save them.
  • A vault credential never touches your directory, so there is no multi-factor prompt for it to fail.
  • When a vault credential and an Entra ID account have the same name, Sendman checks the vault first.
  • An account in a domain federated to AD FS signs in with a vault credential, unless your tenant lets Entra ID check its synced password.
mfp-3f-canon.contoso.local → SendmanNTLM
AUTH NTLM TlRMTVNTUAABAAAAB4IIog…334 TlRMTVNTUAACAAAADAAMADgAAAAF…TlRMTVNTUAADAAAAGAAYAEgAAAAYABgAYAAAAAwA…235 Authentication successful. Let's send some emails!MAIL FROM:<scan@contoso.com>250 2.1.0 Sender OK

Questions about signing in

01Do we have to register anything in our Entra tenant?

No. Sendman validates device credentials against Microsoft Entra ID with no app registration, no consent and nothing to change in your tenant. Hybrid logins such as CONTOSO\svc-scan work as they are.

02What about multi-factor authentication on those accounts?

Neither gets in the way. A vault credential never touches your directory, so there is nothing to prompt for. Entra ID accounts work as well: multi-factor authentication and Conditional Access do not stand in the way, even with strict policies, and the device never sees a prompt. What an account may send as, and to whom, is not a mailbox permission in Exchange Online but a Sendman policy: sender and recipient rules decide, for vault credentials and Entra ID accounts alike.

03Can a device keep the user name it has today?

Yes. A vault credential can carry the name the device already uses, CONTOSO\svc-scan included, and an Entra ID account signs in with its user principal name or, if it is synced from Active Directory, with its domain login.

04Which login mechanisms does Sendman accept?

LOGIN, PLAIN and NTLM. LOGIN and PLAIN work with Entra ID accounts and with vault credentials, NTLM with vault credentials only.

Request a preview and sign in one device with its own login.