ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Why a one size fits all Single Sign-On won't work today

Updated on April 5, 2016

Ever imagined living without your mobile phone? It definitely would feel good to run away from the constant buzzing of the phone for a little while but for most people that’s just dream. Even if some people do realize that dream, it’s definitely going to be a short one.

Grasping that smartphones are your customers’ constant companions, it is only intuitive that your customer’s smartphone is always a part of your marketing and tech strategy irrespective of whichever solution you are preparing to employ. And the same goes Single Sign-On. A true Single Sign On is extremely hard to find or even describe considering different people interpret it differently, it is important to understand how different Single Sign-On solutions work and which one you need so you can provide your customers with the same seamless experience on their mobile phones as well.

Well, it is a common misconception that the only difference between Enterprise Single Single-On and Web Single Sign-On is the environment in which they are deployed to work. Well, that’s a fallacy and if you think you can pick an Enterprise Single Sign-On product and just translate it to Web Single Sign-On, you are deeply mistaken. Enterprise Single Sign-On solutions have an architecture made of agents installed on each of the network’s workstation. Such an architecture is not possible in case of web interface Single Sign-On for obvious reasons. If you are looking to implement a Single Sign-On application for your business, a Web Single Sign-On solution would be the obvious choice but not sufficient. Web Single Sign-On solutions are mostly Security Assertion Markup Language (SAML) based which is not enough when you are talking about reaching mobile devices. SAML is one of the most preferred technologies when it comes to Federation and Single Sign-On but it still recognizes every end user as a web browser which might not always work in case of mobile devices since apps have already taken over smartphones. For your Single Sign-On solution to cover mobile devices, it is important that it support the OAuth 2.0 standards which is app-friendly and defines mobile use cases as well.

But that’s not all, password fatigue is one of the reasons to implement a Single Sign-On and, contrary to general belief, it is just one minor factor. Security is a key consideration while implementing Single Sign-On and the same checkboxes found in a web browser based setup don’t apply to a mobile environment. On a mobile device, the quotient of user-friendliness needs to be much higher than on a desktop based web browser considering the geometry and usage of the smartphones. For this reason, it is important that the Single Sign-On solution employ a multi-factor authentication or an on demand one time password for improved security. Also, it goes without saying that a Risk based authentication system also be employed in order to further improve the security. The topography of the internet or rather the Internet of Things is fast changing and a one size fits all approach simply doesn’t work anymore.


    0 of 8192 characters used
    Post Comment

    No comments yet.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)