Sign-in with SSO and LDAP

Why organisations want it

In large organisations, the IT team does not want to manage users separately in every application. Signing in through the company directory keeps the password policy in one place, inherits multi-factor authentication from the existing system and closes a leaver's access in one step. It is also a common question in information security audits.

How it could work with MIA

Today MIA works with its own user accounts. There is no default admin password, passwords are stored hashed with scrypt, and login attempts are limited. Yönetici (admin), Editör and İzleyici (viewer) roles and an audit log are ready. Organisation sign-in can be added to this for your installation: connecting to an in-house Active Directory or LDAP server, or signing in through identity providers such as Microsoft Entra ID or Google Workspace with SAML or OpenID Connect. Directory groups could map to MIA roles, so that everyone in one group signs in as an Editör, for example. The audit log would record the changes made by people signing in this way just as it does today. Because MIA runs on your own server, the connection can stay inside your network.

What we need to know to scope it

• The directory or identity provider you use
• Whether the MIA server can reach it over the network
• How groups should map to roles
• Whether a local admin account should be kept for emergencies

With this we would suggest a short technical call with your IT team first. Scope, timing and price are agreed for each project.