As an applications developer at ConAgra Foods, one of the most maligned elements to our applications is the need to constantly sign in. Our Remedy implementation until very recently required users to enter their AD username and password upon launch, and worse yet, our SAP implementation required users to enter a separate password (different from their AD password) for each SAP system (CRM, SEM, R/3).
Now that we begin looking toward mobile application development, the need for a single-sign-on approach nears. What follows, then, are the considerations for an SSO solution.
Ease of Use
Users should simply be able to open an application on their mobile device (I would imagine we'd target webOS and iPhone OS initially) and that application should be able to log on to the network without a user entering their username or password.
Ideally, there would be a way to securely identify
Security
Necessary would be the ability to lock out phones. If a user loses their phone, for instance, we need a way to disable network access.
Access to Network Resources
Any SSO solution would need to be able to get past the company firewall and into network resources.
Tuesday, August 17, 2010 at 9:08AM ;)
It's a beautiful campus and a great addition to the Omaha skyline. It will certainly bring visibility to TD Ameritrade. Here's a rendering of the campus at night:;)
