So, what's the hype these days? Cloud, Mobile, Social. You can't run away from these 3 themes.
Today, I came across Oracle Mobile and Social Access Management.
We should chop it into 2 components:
- Mobile Access Management; and
- Social Access Management
Social Access Management is nothing but OAuth and OpenID authentication. OMSS (Oracle Mobile and Social Server) now supports Google, Yahoo, Facebook, Twitter, or LinkedIn. (so besides OAuth 2.0, it does support OAuth 1.0)
Mobile Access Management is something like a ESSO on a mobile platform.
Yes, I know traditional WSSO people will be very much against developing something that is beyond web. But, hey, what are the 3 current themes these days? Cloud, Mobile, Social.
If we are going to survive, we should adopt the trend and not stay away from it.
Yes, it's troublesome to develop a SDK for iOS and yet another SDK for Android. But this is what customers want. Who are the potential customers?
I can foresee big insurance companies wanting to adopt this solution for their multiple mobile applications for insurance agents who are always on the mobile. These applications would need to be single-sign-on so as to save the agents's time while serving customers.
I can also foresee big banks waiting to adopt this solution for their mobile applications for the private bankers who are also always on the move.
These are big customers who do not need features rich Single Sign-On solutions, but specific needs to their critical and money-making applications for their mobile employees. And not forgetting, these are good willing paying customers. :)
.
Mobile Access Management is something like a ESSO on a mobile platform.
Yes, I know traditional WSSO people will be very much against developing something that is beyond web. But, hey, what are the 3 current themes these days? Cloud, Mobile, Social.
If we are going to survive, we should adopt the trend and not stay away from it.
Yes, it's troublesome to develop a SDK for iOS and yet another SDK for Android. But this is what customers want. Who are the potential customers?
I can foresee big insurance companies wanting to adopt this solution for their multiple mobile applications for insurance agents who are always on the mobile. These applications would need to be single-sign-on so as to save the agents's time while serving customers.
I can also foresee big banks waiting to adopt this solution for their mobile applications for the private bankers who are also always on the move.
These are big customers who do not need features rich Single Sign-On solutions, but specific needs to their critical and money-making applications for their mobile employees. And not forgetting, these are good willing paying customers. :)
.
No comments:
Post a Comment