Hi. We use some Oracle products (Webcenter, SSXA, IRM, UBR, UCM, SOA BPM, WC_COlaboration, etc).
We need to connect these applications with other external applications using CAS (SSO). We think the solution is change the Authentication Provider in Oracle Weblogic Security Realms config. But when we was reading the options in authentication provider menu, does not appear any option for CAS: ------------------------ WebLogic Server offers the following types of Authentication providers: The WebLogic Authentication provider accesses user and group information in WebLogic Server’s embedded LDAP server. LDAP Authentication providers access external LDAP stores. You can use an LDAP Authentication provider to access any LDAP server. WebLogic Server provides LDAP Authentication providers already configured for Open LDAP, Sun iPlanet, Microsoft Active Directory and Novell NDS LDAP servers. RDBMS Authentication providers access external relational databases. WebLogic Server provides three RDBMS Authentication providers: SQL Authenticator, Read-only SQL Authenticator, and Custom RDBMS Authenticator. The WebLogic Identity Assertion provider validates X.509 and IIOP-CSIv2 tokens and optionally can use a user name mapper to map that token to a user in a WebLogic Server security realm. The SAML Authentication provider, which authenticates users based on Security Assertion Markup Language 1.1 (SAML) assertions. The Negotiate Identity Assertion provider, which uses Simple and Protected Negotiate (SPNEGO) tokens to obtain Kerberos tokens, validates the Kerberos tokens, and maps Kerberos tokens to WebLogic users. The SAML Identity Assertion provider, which acts as a consumer of SAML security assertions. This enables WebLogic Server to act as a SAML destination site and supports using SAML for single sign-on. In addition, you can use: Custom (non-WebLogic) Authentication providers, which offer different types of authentication technologies. Custom (non-WebLogic) Identity Assertion providers, which support different types of tokens. ----------------------- We think that we need to implement a new Authentication Provider. Is that correct? Or any other idea? Thanks. -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
