Prior to the introduction Oracle9iAS SSO, each component within Oracle9iAS required separate password and authentication management. Besides the duplication of passwords, the lack of a unified security interface presented a huge maintenance issues and also compromised the overall manageability of the application.
Without SSO, every user is required to maintain a distinct password for every application in the enterprise. As anyone who has dozens of passwords can tell you, they must write-down the passwords, which can cause a serious security breach. With SSO, each user has only one password for all applications within the Oracle9iAS framework.
Unlike traditional Oracle applications, SSO is designed for web-based users. Any Oracle system can be web-enabled, and the end-user community can securely access their applications from the Internet, anywhere in the world. The central components of Oracle9iAS SSO are the mod_osso module and the SSO login server, and that will be the focus of our SSO exploration. As an Oracle9iAS administrator, you are responsible for maintaining enterprise security, and knowledge of SSO administration is required.
Oracle9iAS uses two techniques for end-user authentication, one for local “partner” applications (internal) and another for external applications. Because of the infinite possible authentication mechanisms of external applications, they cannot be integrated into SSO and LDAP entries are used to manage security.
Read more here:
Need a Health Check?
Oracle is the worlds most complex and robust database and there are hundreds of sub-optimal setting that can cripple your database performance.
Burleson Consulting has a great Oracle health check where we identify all database bottlenecks to ensure that your mission-critical system is running at optimal speeds.
Just call 800-766-1884 to schedule your health check.