I have mentioned 'Zero Sign-On' in past blogs, but in this blog wanted to explain the differences between Zero Sign-On (ZSO) and Single Sign-On (SSO).
Both ZSO and SSO means you have one username and password (e.g. your Active Directory username and password; people often refer to the two combined together as your Active Directory ID) across a plethora of apps and operating systems. Note I included operating systems — be it mobile, PC, Mac or server OSes such as Linux or UNIX or Windows — as people log into those systems every day just like they log into apps. [Many SSO vendors conveniently forget to mention that many people log onto multiple systems and devices each day, especially if they are an IT person. Maybe it's because they only support SaaS apps.]
The core difference is usually that SSO means you have to re-enter the username and password, i.e. your ID, every time you log into a system or app. Granted it is better that you have a single ID vs. multiple IDs, but it is pain in the butt to have to re-enter the same ID over and over again every time you log onto a new app etc..
ZSO is about silent authentication, that once you are initially authenticated, that you never have to type in your ID again when you launch an app or say SSH into another system etc. I sometimes refer to ZSO as 1-click access, i.e. click on the app and you auto-magically authenticate and there is no prompting for a username and password. And of course do so in a secure manner using secure protocols (vs. storing/caching credentials on a local device).
ZSO is very important on mobile devices, especially for rich mobile apps. The reason being is that the form factor of a mobile device (e.g. smartphone) is such that even if you had a relatively simple username and password, odds are you going to screw up typing that username and password in, and a simple login process may end up being 30 seconds to a 1 minute process. Because 'who has time for something like this':
I have mentioned 'Zero Sign-On' in past blogs, but in this blog wanted to explain the differences between Zero Sign-On (ZSO) and Single Sign-On (SSO).Both ZSO and SSO means you have one username and password (e.g. your Active Directory username and password; people often refer to the two combined together as your Active Directory ID) across a plethora of apps and operating systems. Note I included operating systems — be it mobile, PC, Mac or server OSes such as Linux or UNIX or Windows — as people log into those systems every day just like they log into apps. [Many SSO vendors conveniently forget to mention that many people log onto multiple systems and devices each day, especially if they are an IT person. Maybe it's because they only support SaaS apps.]The core difference is usually that SSO means you have to re-enter the username and password, i.e. your ID, every time you log into a system or app. Granted it is better that you have a single ID vs. multiple IDs, but it is pain in the butt to have to re-enter the same ID over and over again every time you log onto a new app etc..ZSO is about silent authentication, that once you are initially authenticated, that you never have to type in your ID again when you launch an app or say SSH into another system etc. I sometimes refer to ZSO as 1-click access, i.e. click on the app and you auto-magically authenticate and there is no prompting for a username and password. And of course do so in a secure manner using secure protocols (vs. storing/caching credentials on a local device).
ZSO is very important on mobile devices, especially for rich mobile apps. The reason being is that the form factor of a mobile device (e.g. smartphone) is such that even if you had a relatively simple username and password, odds are you going to screw up typing that username and password in, and a simple login process may end up being 30 seconds to a 1 minute process. Because 'who has time for something like this':
การแปล กรุณารอสักครู่..