1 / 12

Enterprise Single Sign On

Enterprise Single Sign On. Identity management for web applications. What is Single Sign On.

lincoln
Download Presentation

Enterprise Single Sign On

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Single Sign On Identity management for web applications

  2. What is Single Sign On • Single sign-on (SSO) is a mechanism whereby a single action of user authentication and authorization can permit a user to access all computers and systems where he has access permission, without the need to enter multiple passwords

  3. SSO with Web Booster • Authenticates with Microsoft Windows, creates access tokens for other systems • Users logged in to their workstation can auto-login to web applications

  4. Benefits to Users • Only have one username and password to remember • No more post-it! notes on monitor with account details • Fast • Seamless • Works with BlackBerry handheld devices

  5. Benefits to Operations Staff • Central user account management • Common way to manage accounts • Web Booster ESSO is quick to deploy • No changes to existing servers • No more post-it! notes ;-)

  6. Security • Choose between NTLM or Kerberos authentication • All data is encrypted and verified against Windows Domain Controllers or KDC servers • Traffic to browser may be SSL encrypted

  7. Built on Web Booster • Get all existing Booster features • Content compression • Clustering • Load sharing • Dynamic failover • …plus much more

  8. Considerations • Need to ensure workstations are not compromised or left unattended • Windows Domain structure may need to be rationalized for NTLM to work correctly • Need to identify weak spots in infrastructure to avoid single failure points, eg: LDAP

  9. NTLM vs Kerberos • NTLM more widely supported in older versions of Windows (pre win2K) • NTLM is easier to configure initially • Kerberos is more secure • Kerberos is not tied to Windows

  10. Requirements • Windows workstations • Windows domain • Lotus Domino and/or IBM WebSphere servers (more coming soon)

  11. Who uses Web Booster? Some of our customers include…

  12. Questions… • Email: info@puakma.net • Web: http://www.puakma.net/booster • Contact one of our business partners

More Related