In its My-Access offering, Memority provides a set of mechanisms for organizing and personalizing user authentication to federated applications, depending on their identity, the device and network they are using, and the application they wish to access. With Memority, we adapt!
Setting the scene
To better understand how to manage multiple means of identification from a single source, let's imagine a company, which we'll call myCompany. In myCompany, we have, of course, internal employees, but also service providers. The myCompany employees have access to the hardware provided by the company - PC and smart card, for example - enabling them to access IS applications. Service providers, on the other hand, come to myCompany using their own equipment (supplied by their service company). They still need to be able to access myCompany IS applications in order to carry out their work properly. Let's find out how.
Internal employees
To make authentication as smooth as possible for internal employees, Memority is able to offer them a range of authentication methods, such as Kerberos, Windows Hello or smart card authentication, and, in addition, to set up context-dependent adaptive authentication rules. For example, Kerberos authentication can be triggered automatically and directly if the user is not on a cell phone. If this is valid, authentication is totally transparent to the user. If, on the other hand, Kerberos authentication fails (because the user is not on the myCompany network and/or not on a PC supplied by myCompany), then the other authentication modes available depending on the context can be proposed, such as the smart card, if this is detected on the workstation, or Windows Hello, if the user has previously enrolled Windows Hello on the myCompany workstation. But what happens if an employee needs to access certain applications from a cell phone? As the previous authentication methods are limited to the PC, it is possible to add another method, such as login/password, which would then be available only to employees, and only on a mobile device. myCompany employees would then have 4 different means of authentication to access IS applications. What a choice!
