Skip to main content

Authentication Types

There are two login mechanisms in Dime.Scheduler.

Microsoft Entra ID​

Users can log in to Azure with their Microsoft credentials, which then passes a set of claims to Dime.Scheduler. This means that Dime.Scheduler does not store any credentials, it can only work with the data that the administrator has granted. The MS Entra ID App Registration only needs your email address to authenticate, otherwise no other permissions are required.

tip

Users can individually grant consent, or the administrator can grant consent on behalf of the organization. For production, click here. To grant access to users on the sandbox, click here.

You have seen it before, other websites allowing you to log in with your Facebook or Google account. This is very much like that. Dime.Scheduler can use only so much of the information granted by Microsoft and the administrator. This is beneficial for both Dime Software and the users: instead of having to store separate credentials for every application (and then forgetting the password for each and every one of them), some other website's identity system can be used. In terms of security, this is also a better option since the onus is on Microsoft to ensure a secure identity management system. We are confident in our own capabilities but Microsoft just has more resources to do the job.

Forms​

The forms authentication mechanism is a standard password protected system. It is secure and adheres to the industry standards. Administrators can manually create users in the system using the provided setup view. Users will receive a welcome e-mail and will automatically be prompted to reset the password.

Just like any other web application, there is no need to panic when the user forgets his password. In the login view there is a link that will help the user to securely reset it.

Read more​