Auditing is the process whereby information about operating requests and the outcome of those requests are collected, stored, and distributed for the purposes of non-repudiation. In other words, auditing provides an electronic trail of computer activity. In the WebLogic Server security architecture, an Auditing provider is used to provide auditing services.
If configured, the WebLogic Security Framework will call through to an Auditing provider before and after security operations (such as authentication or authorization) have been performed, when changes to the domain configuration are made, or when management operations on any resources in the domain are invoked. The decision to audit a particular event is made by the Auditing provider itself and can be based on specific audit criteria and/or severity levels. The records containing the audit information may be written to output repositories such as an LDAP server, database, and a simple file.
Authentication is the process of deriving the identity of the users or system processes. WebLogic Server provides authentication services through Authentication providers. Learn about the authentication concepts and functionality.
Authentication is the mechanism by which callers prove that they are acting on behalf of specific users or systems. Authentication answers the question, "Who are you?" using credentials such as username/password combinations.
In WebLogic Server, Authentication providers are used to prove the identity of users or system processes. Authentication providers also remember, transport, and make identity information available to various components of a system (via subjects) when needed. During the authentication process, a Principal Validation provider provides additional security protections for the principals (users and groups) contained within the subject by signing and verifying the authenticity of those principals.
The following sections describe authentication concepts and functionality.
Subjects and Principals
A principal is an identity assigned to a user or group as a result of authentication. Both users and groups can be used as principals by application servers such as WebLogic Server. The Java Authentication and Authorization Service (JAAS) requires that subjects be used as containers for authentication information, including principals.
Figure 3-1 illustrates the relationships among users, groups, principals, and subjects.
Figure 3-1 Relationships Among Users, Groups, Principals, and Subjects
Description of "Figure 3-1 Relationships Among Users, Groups, Principals, and Subjects"
As part of a successful authentication, principals are signed and stored in a subject for future use. A Principal Validation provider signs principals, and an Authentication provider's LoginModule actually stores the principals in the subject. Later, when a caller attempts to access a principal stored within a subject, a Principal Validation provider verifies that the principal has not been altered since it was signed, and the principal is returned to the caller (assuming all other security conditions are met).
Any principal that is going to represent a WebLogic Server user or group needs to implement the
WLSGroup interfaces, which are available in the
Java Authentication and Authorization Service (JAAS)
Whether the client is an application, applet, Enterprise JavaBean (EJB), or servlet that requires authentication, WebLogic Server uses the Java Authentication and Authorization Service (JAAS) classes to reliably and securely authenticate to the client.
JAAS implements a Java version of the Pluggable Authentication Module (PAM) framework, which permits applications to remain independent from underlying authentication technologies. Therefore, the PAM framework allows the use of new or updated authentication technologies without requiring modifications to your application.
WebLogic Server uses JAAS for remote fat-client authentication, and internally for authentication. Therefore, only developers of custom Authentication providers and developers of remote fat client applications need to be involved with JAAS directly. Users of thin clients or developers of within-container fat client applications (for example, those calling an Enterprise JavaBean (EJB) from a servlet) do not require the direct use or knowledge of JAAS.
A LoginModule is the work-horse of authentication: all LoginModules are responsible for authenticating users within the security realm and for populating a subject with the necessary principals (users/groups). LoginModules that are not used for perimeter authentication also verify the proof material submitted (for example, a user's password).
If there are multiple Authentication providers configured in a security realm, each of the Authentication providers' LoginModules will store principals within the same subject. Therefore, if a principal that represents a WebLogic Server user (that is, an implementation of the
WLSUser interface) named "Joe" is added to the subject by one Authentication provider's LoginModule, any other Authentication provider in the security realm should be referring to the same person when they encounter "Joe". In other words, the other Authentication providers' LoginModules should not attempt to add another principal to the subject that represents a WebLogic Server user (for example, named "Joseph") to refer to the same person. However, it is acceptable for another Authentication provider's LoginModule to add a principal of a type other than
WLSUser with the name "Joseph".
JAAS Control Flags
If a security realm has multiple Authentication providers configured, the Control Flag attribute on the Authenticator provider determines the ordered execution of the Authentication providers. The values for the Control Flag attribute are as follows:
REQUIRED - This LoginModule must succeed. Even if it fails, authentication proceeds down the list of LoginModules for the configured Authentication providers. This setting is the default.
REQUISITE - This LoginModule must succeed. If other Authentication providers are configured and this LoginModule succeeds, authentication proceeds down the list of LoginModules. Otherwise, return control to the application.
SUFFICIENT - This LoginModule needs not succeed. If it does succeed, return control to the application. If it fails and other Authentication providers are configured, authentication proceeds down the LoginModule list.
OPTIONAL - The user is allowed to pass or fail the authentication test of this Authentication providers. However, if all Authentication providers configured in a security realm have the JAAS Control Flag set to OPTIONAL, the user must pass the authentication test of one of the configured providers.
A CallbackHandler is a highly-flexible JAAS standard that allows a variable number of arguments to be passed as complex objects to a method. There are three types of CallbackHandlers:
TextInputCallback, all of which are part of the
PasswordCallback return the username and password, respectively.
TextInputCallback can be used to access the data users enter into any additional fields on a login form (that is, fields other than those for obtaining the username and password). When used, there should be one
TextInputCallback per additional form field, and the prompt string of each
TextInputCallback must match the field name in the form. WebLogic Server only uses the
TextInputCallback for form-based Web application login.
An application implements a
CallbackHandler and passes it to underlying security services so that they may interact with the application to retrieve specific authentication data, such as usernames and passwords, or to display certain information, such as error and warning messages.
CallbackHandlers are implemented in an application-dependent fashion. For example, implementations for an application with a graphical user interface (GUI) may pop up windows to prompt for requested information or to display error messages. An implementation may also choose to obtain requested information from an alternate source without asking the user.
Underlying security services make requests for different types of information by passing individual
Callbacks to the
CallbackHandler implementation decides how to retrieve and display information depending on the
Callbacks passed to it. For example, if the underlying service needs a username and password to authenticate a user, it uses a
CallbackHandler can then choose to prompt for a username and password serially, or to prompt for both in a single window.
With mutual authentication, both the client and the server are required to authenticate themselves to each other. This can be done by means of certificates or other forms of proof material.
WebLogic Server supports two-way SSL authentication, which is a form of mutual authentication. However, by strict definition, mutual authentication takes place at higher layers in the protocol stack then does SSL authentication. See One-way/Two-way SSL Authentication.
Identity Assertion Providers and LoginModules
When used with a LoginModule, Identity Assertion providers support single sign-on. For example, an Identity Assertion provider can process a SAML assertion so that users are not asked to sign on more than once.
The LoginModule that an Identity Assertion provider uses can be:
Part of a custom Authentication provider you develop.
Part of the WebLogic Authentication provider that Oracle developed and packaged with WebLogic Server.
Part of a third-party security vendor's Authentication provider.
Unlike in a simple authentication situation, the LoginModules that Identity Assertion providers use do not verify proof material such as usernames and passwords; they simply verify that the user exists.
Identity Assertion and Tokens
Identity Assertion providers support user name mappers, which map a valid token to a WebLogic Server user.
You develop Identity Assertion providers to support the specific types of tokens that you will be using to assert the identities of users or system processes. You can develop an Identity Assertion provider to support multiple token types, but the WebLogic Server administrator must configure the Identity Assertion provider so that it validates only one "active" token type. While you can have multiple Identity Assertion providers in a security realm with the ability to validate the same token type, only one Identity Assertion provider can actually perform this validation.
To use the WebLogic Identity Assertion provider for X.501 and X.509 certificates, you have the option of using the default user name mapper that is supplied with the WebLogic Server product
(weblogic.security.providers.authentication. DefaultUserNameMapperImpl) or providing your own implementation of the
weblogic.security.providers.authentication.UserNameMapper interface. See Do You Need to Develop a Custom Identity Assertion Provider? in Developing Security Providers for Oracle WebLogic Server.
Challenge Identity Assertion
Challenge identity assertion schemes provide for multiple challenges, responses messages, and state.
A WebLogic Server security realm can include security providers that support authentication protocols such as Microsoft's Windows NT Challenge/Response (NTLM), Simple and Protected GSS-API Negotiation Mechanism (SPNEGO), and other challenge/response authentication mechanisms. WebLogic Server includes a SPNEGO security provider, named the Negotiate Identity Assertion provider. You can develop and deploy security providers that implement NTLM or other challenge/response authentication mechanisms. See Identity Assertion Providers in Developing Security Providers for Oracle WebLogic Server.
Servlet Authentication Filters
A Servlet Authentication filter is an extension of the filter object that overcomes these drawbacks, allowing filters to replace container-based authentication.
As defined by the Java Servlet API specification, filters are objects that can modify a request or response. Filters are preprocessors of the request before it reaches the servlet, and/or postprocessors of the response leaving the servlet. Filters provide the ability to encapsulate recurring tasks in reusable units.
Filters can be used as a substitute for container-based authentication but there are some drawbacks to this design:
As specified by the Java Servlet API specification, filters are run after authentication and authorization. If filters are used for authentication, they must also be used for authorization thereby preventing container-managed authorization from being used. Most use cases that require extensions to the authentication process in the Servlet container do not require extensions to the authorization process. Having to implement the authorization process in a filter is awkward, time consuming, and error-prone.
Java EE filters are defined per Web application. Code for a filter must reside in the WAR file for the Web application and the configuration must be defined in the
web.xmlfile. An authentication mechanism is typically determined by the system administrator after an application is written (not by the programmer who created the WAR file). The mechanism can be changed during the lifetime of an application, and is desired for all (or at least most) applications in a site.
JAAS LoginModules (within a WebLogic Authentication provider) can be used for customization of the login process. Servlet Authentication filters enable the LoginModule model allowing the authentication provider to control the actual conversation with the client. Customizing the location of the user database, the types of proof material required to execute a login, or the population of the Subject with groups is implemented via a LoginModule. On the other hand, redirecting to a remote site to execute the login, extracting login information out of the query string, and negotiating a login mechanism with a browser is implemented via a Servlet Authentication filter.
Types of Authentication
WebLogic Server users must be authenticated whenever they request access to a protected WebLogic resource. Each user is required to provide a credential (for example, a password) to WebLogic Server. WebLogic Server provides a set of Authentication providers to perform different types of authentication. You can also create a customer security provider to handle your specific authentication needs.
The following types of authentication are supported by the WebLogic Authentication provider that is included in the WebLogic Server distribution:
WebLogic Server can use the WebLogic Authentication provider that is provided as part of the WebLogic Server product or custom security providers to perform the different types of authentication. For information on the WebLogic Authentication provider and how to configure authentication, see The Authentication Process and the following sections in Administering Security for Oracle WebLogic Server:
In username/password authentication, a user ID and password are requested from the user and sent to WebLogic Server. WebLogic Server checks the information and if it is trustworthy, grants access to the protected WebLogic resource.
Secure Sockets Layer (SSL), or Hyper-Text Transfer Protocol (HTTPS), can be used to provide an additional level of security to username/password authentication. Because SSL encrypts the data transferred between the client and WebLogic Server, the user ID and password of the user do not flow in the clear. Therefore, WebLogic Server can authenticate the user without compromising the confidentiality of the user's ID and password.
When an SSL or HTTPS client request is initiated, WebLogic Server responds by presenting its digital certificate to the client. The client then verifies the digital certificate and an SSL connection is established. The digital certificate is issued by an entity (a trusted certificate authority), which validates the identity of WebLogic Server.
You can also use two-way SSL authentication, a form of mutual authentication. With two-way SSL authentication, both the client and server must present a certificate before the connection thread is enabled between the two. See One-way/Two-way SSL Authentication.
Two-way SSL authentication is supported by the WebLogic Authentication provider that is provided as part of the WebLogic Server product.
Using digest authentication enables the storage of password information that is required to support Web Services Security Password Digest.
When using digest authentication, the client makes an un-authenticated request to the server, and the server sends a response with a digest authentication challenge indicating that it supports digest authentication. The client generates a nonce and sends it to the server along with a timestamp, digest, and username. The digest is a cyptographic hash of the password, nonce, and timestamp. The client requests the resource again this time sending the username and a cyptographic hash of the password combined with the nonce value. The server generates the hash itself, and if the generated hash matches the hash in the request, the request is allowed.
The advantage of digest authentication is it is resistant to replay attacks. The implementation maintains a cache of used nonces/timestamps for a specified period of time. All requests with a timestamp older than the specified timestamp are rejected as well as any requests that use the same timestamp/nonce pair as the most recent timestamp/nonce pair still in the cache. WebLogic Server stores this cache in a database.
Perimeter authentication is used to authenticate the identity of a remote user outside of the application server domain. WebLogic Server supports SAML and SPNEGO perimeter authentication schemes.
The following sections describe perimeter authentication:
How is Perimeter Authentication Accomplished?
Perimeter authentication is typically accomplished by the remote user specifying an asserted identity and some form of corresponding proof material, normally in the form of a passphrase (such as a password, a credit card number, Personal Identification Number, or some other form of personal identification information), which is used to perform the verification.
The authentication agent, the entity that actually vouches for the identity, can take many forms, such as a Virtual Private Network (VPN), firewall, an enterprise authentication service, or some other form of global identity service. Each of these forms of authentication agents has a common characteristic: they all perform an authentication process that results in an artifact or token that must be presented to determine information about the authenticated user at a later time. Currently, the format of the token varies from vendor to vendor, but there are efforts to define a standard token format using XML. In addition, there is a current standard for Attribute Certificates, which is based on the X.509 standard for digital certificates. But even after all of this, if the applications and the infrastructure on which they are built are not designed to support this concept, enterprises are still forced to require that their remote users re-authenticate to the applications within the network.
How Does WebLogic Server Support Perimeter Authentication?
WebLogic Server is designed to extend the single sign-on concept all the way to the perimeter through support for identity assertion (see Figure 3-2). Provided as a critical piece of the WebLogic Security Framework, the concept of identity assertion allows WebLogic Server to use the authentication mechanism provided by perimeter authentication schemes such as the Security Assertion Markup Language (SAML), the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO), or enhancements to protocols such as Common Secure Interoperability (CSI) v2 to achieve this functionality.
Figure 3-2 Perimeter Authentication
Description of "Figure 3-2 Perimeter Authentication"
Support for perimeter authentication requires the use of an Identity Assertion provider that is designed to support one or more token formats. Multiple and different Identity Assertion providers can be registered for use. The tokens are transmitted as part of any normal business request, using the mechanism provided by each of the various protocols supported by WebLogic Server. Once a request is received with WebLogic Server, the entity that handles the processing of the protocol message recognizes the existence of the token in the message. This information is used in a call to the WebLogic Security Framework that results in the appropriate Identity Assertion provider being called to handle the verification of the token. It is the responsibility of the Identity Assertion provider implementation to perform whatever actions are necessary to establish validity and trust in the token and to provide the identity of the user with a reasonable degree of assurance, without the need for the user to re-authenticate to the application.
Security Assertion Markup Language (SAML)
SAML provides single sign-on capability for web applications to ensure that user identities can be shared and protected, and allows for exchanging identity information between software entities. WebLogic Server supports SAML 1.1. and 2.0, SAML Web SSO profile, and the Web Services SAML Token Profile.
The SAML standard defines a common XML framework for creating, requesting, and exchanging security assertions between software entities on the Web. This framework specifies how SAML assertions and protocols may be used to provide the following:
Browser-based single sign-on (SSO) between online business partners
The exchange of identity information in web services security
SAML was developed by the Organization for the Advancement of Structured Information Standards (OASIS), and this release of WebLogic Server includes broad support for SAML 1.1 and 2.0, including support for the following:
SAML Web SSO profile
The SAML Web SSO profile specifies how SAML assertions and protocols should be used to provide browser-based single sign-on between an Identity Provider (a producer of assertions) and a Service Provider (a consumer of assertions).
In the SAML 2.0 Web SSO profile, a web user either invokes a resource hosted by a Service Provider site, or accesses an Identity Provider site in a way that results in an invocation on a resource hosted by the Service Provider. In either case, the web user is authenticated by the Identity Provider, which in turn generates an assertion on behalf of that user that contains information about the user's identity. The Identity Provider sends the assertion to the Service Provider, which consumes the assertion by extracting identity information about the user that is mapped to a Subject in the local security realm.
Web Services Security (WS-Security) SAML Token profile 1.1
The SAML Token profile is part of the core set of WS-Security standards, and specifies how SAML assertions can be used for Web services security. WebLogic Server supports SAML Token Profile 1.1, including support for SAML 2.0 and SAML 1.1 assertions. SAML Token Profile 1.1 is backwards compatible with SAML Token Profile 1.0.
The following sections introduce how SAML is supported in WebLogic Server:
SAML Framework Concepts
The SAML framework is based on the following concepts.
The terms for these concepts differ somewhat between SAML 1.1 and 2.0, particularly regarding how the entities to which they correspond are represented in the WebLogic Server Administration Console, as described in this section.
Identity Provider - A system, or administrative domain, that asserts that a user has been authenticated and is given associated attributes. For example, there is a user John Doe, he has an email address of firstname.lastname@example.org and he authenticated to this domain using a password mechanism. An Identity Provider is also known as a SAML authority, asserting party, or source site, and is often abbreviated as IdP.
You can configure a WebLogic Server instance to act in the role of Identity Provider. An Identity Provider is known by its Issuer URI (name). The SAML credential mapping provider supplies this functionality in WebLogic Server. (Note that the specific credential mapping provider you configure is specific to the version of SAML you are using.)
When you configure SAML 1.1 services in a WebLogic Server instance, the WebLogic Server Administration Console uses the term source site in place of Identity Provider.
Service Provider - A system, or administrative domain, that determines whether it trusts the assertions provided to it by the Identity Provider. SAML defines a number of mechanisms that enable the Service Provider to trust the assertions provided to it. A Service Provider is also known as a relying party, or destination site, and is often abbreviated as SP.
Although a Service Provider may trust the assertions provided to it, local access policy defines whether the subject may access local resources. Therefore, even if a Service Provider trusts that a user is Dan Murphy, it does not mean Dan Murphy can access all the resources in the domain.
You can configure a WebLogic Server instance to act in the role of Service Provider. Trust relationships with Identity Provider partners must be established. The SAML identity assertion provider supplies this functionality in WebLogic Server. (Note that the specific identity assertion provider you configure is specific to the version of SAML you are using.)
When you configure SAML 1.1 services in a WebLogic Server instance, the WebLogic Server Administration Console uses the term destination site in place of Service Provider.
Assertion - An assertion is a package of information that supplies one or more statements made by an Identity Provider. The following types of statements are supported:
Authentication statements, which say when and how a subject was authenticated.
Attribute statements, which provide specific information about the subject (for example, what groups the Subject is a member of).
Authorization statements identity what the Subject is entitled to do.
Note the following regarding SAML assertions in WebLogic Server:
Attribute statements are supported only for the purpose of including group information. The SAML Authentication provider can retrieve group information from a SAML assertion (see Configuring the SAML Authentication Provider in Administering Security for Oracle WebLogic Server.)
SAML authorization is not supported in this release of WebLogic Server.
Protocols - SAML defines a number of request/response protocols for obtaining assertions. A SAML request can ask for a specific known assertion or make authentication or attribute decision queries, with the SAML response providing back the requested assertions. The XML format for protocol messages with their allowable extensions is defined in an XML schema.
WebLogic Server supports the authentication request protocol, which defines an authentication request (that is, a message containing an
<AuthnRequest>statement) that causes an authentication response (that is, a message containing a
<Response>statement) to be returned. The authentication response contains an assertion that pertains to a Principal.
Typically the authentication request is sent by a Service Provider to an Identity Provider, which returns the authentication response. The authentication request protocol is used to support the Web Browser SSO Profile.
Bindings - Bindings define the lower-level communication or messaging protocols (such as HTTP or SOAP) over which the SAML protocols can be transported. A binding details exactly how the SAML protocol maps onto transport and messaging protocols. For example, the mapping of the SAML
<AuthnRequest>message onto HTTP.
For SAML 1.1, WebLogic Server provides support for HTTP POST and HTTP Artifact as profiles. For SAML 2.0, WebLogic Server provides support for HTTP POST and HTTP Artifact bindings for the Web SSO profile.
For SAML 2.0, WebLogic Server adds the HTTP Redirect binding for the Web SSO profile.
Profiles - Descriptions of particular flows of assertions and protocol messages that define how SAML can be used for a particular purpose. A profile is the combination of protocols, bindings, and the structure of assertions that are used to support a particular use case, such as the Web SSO profile and SAML Token profile supported in WebLogic Server.
Metadata files - SAML 2.0 defines a new metadata schema for exchanging configuration information between partners. WebLogic Server supports this schema by providing the ability to create local site configuration data that is published to a file and shared with partners for use with the Web SSO Profile. Partners subsequently import this metadata file to retrieve this configuration data, which is used to populate partner registries and ensure that SAML messages can be transmitted and consumed more consistently and reliably. Note that metadata files are not used with the WS-Security SAML Token Profile 1.1.
For a complete description of these concepts and how they apply to the SAML architecture, see the following:
For SAML V1.1, see Technical Overview of the OASIS Security Assertion Markup Language (SAML) V1.1 (
For SAML V2.0, see Security Assertion Markup Language (SAML) 2.0 Technical Overview (
SAML Components Provided in WebLogic Server
Support for SAML 1.1 and 2.0 is provided in the following WebLogic Server components:
SAML security providers
Single Sign-On services
Web services support for SAML Token Profile 1.1
SAML Security Providers
WebLogic Server provides the following security providers to support SAML 1.1 and 2.0:
Table 3-1 Security Providers Included in WebLogic Server to Support SAML
|To support . . .||The following provider . . .||Does the following . . .|
SAML Credential Mapping provider Version 2
Generates SAML 1.1 assertions. This provider must be configured for a WebLogic Server instance that serves as an Identity Provider (or, as identified in the WebLogic Server Administration Console, the source site).
SAML Identity Assertion provider Version 2
Consumes SAML 1.1 assertions. This provider must be configured for a WebLogic Server instance that serves as an Service Provider (or, as identified in the WebLogic Server Administration Console, the destination site).
SAML 2.0 Credential Mapping provider
Generates SAML 2.0 assertions. This provider must be configured for a WebLogic Server instance that serves as an Identity Provider.
SAML 2.0 Identity Assertion provider
Consumes SAML 2.0 assertions. This provider must be configured for a WebLogic Server instance that serves as an Service Provider.
SAML 1.1 and 2.0
SAML Authentication provider
Enables "virtual user" functionality for both the SAML 1.1 and SAML 2.0 Identity Assertion providers. (See Configuring the SAML Authentication Provider in Administering Security for Oracle WebLogic Server.)
Single Sign-On Services
WebLogic Server can be configured to act as a SAML Identity Provider (IdP), Service Provider, or both. When acting as an IdP, the SAML credential mapping provider must be configured so that the IdP can produce assertions. When acting as a Service Provider, the SAML identity assertion provider must be configured so that the Service Provider can consume assertions.
SAML Single Sign-On Services (SSO) are configured on a per-server basis. To enable SAML SSO in two or more servers in a domain, such as in a cluster, the recommended approach is to do the following:
- Create a domain in which the RDBMS security store is configured. See Managing the RDBMS Security Store in Administering Security for Oracle WebLogic Server.
- Ensure that SSO services are configured individually and identically on each server instance.
Web Services Support for SAML Token Profile 1.1
WebLogic Server Web services supports SAML Token Profile 1.1. This feature includes support for both SAML 2.0 and SAML 1.1 assertions and is backwards-compatible with SAML Token Profile 1.0.
You configure SAML tokens for a web service through use of the appropriate WS-SecurityPolicy assertions.
SAML Token Profile 1.1 is supported only through WS-SecurityPolicy. The earlier "WLS 9.2 Security Policy" supports SAML Token Profile 1.0/SAML 1.1 only.
When using SAML Token Profile, the appropriate SAML security providers must be configured (either the SAML 2.0 or SAML 1.1 credential mapping or identity assertion providers) depending on the desired SAML version and assertion usage.
Single Sign-On (SSO)
Single sign-on (SSO) enables users to log in securely to an application only once and gain access to many different application components, even if these components have their own authentication schemes.
WebLogic Server provides single sign-on (SSO) with the following environments:
Web Browsers and HTTP Clients via SAML
The Security Assertion Markup Language (SAML) enables cross-platform authentication between Web applications or Web services running in a WebLogic Server domain and Web browsers or other HTTP clients. WebLogic Server supports single sign-on (SSO) based on SAML. When users are authenticated at one site that participates in a single sign-on (SSO) configuration, they are automatically authenticated at other sites in the SSO configuration and do not need to log in separately.
When you use the WebLogic Server Administration Console to configure SAML, you will notice that the names used for some SAML entities differ between SAML 1.1 and 2.0. This section identifies the key terminology differences.
The following steps describe a typical scenario that shows how SAML SSO works.
A Web user attempts to access a target resource at a site that is configured to accept authentications through SAML assertions.
When configuring SAML 1.1 in the WebLogic Server Administration Console, this site is called the destination site. In SAML 2.0, this site is called the Service Provider.
The Service Provider determines that the user's credentials need to be authenticated by a central site that can generate a SAML assertion for that user. The Service Provider redirects the authentication request to that central site.
In SAML 1.1, the site that generates the SAML assertion is called the source site. In SAML 2.0, this site is the Identity Provider. In both SAML versions, this site is sometimes called a SAML Authority.
The user logs in to the Identity Provider site, typically via a login web application hosted by that site. The Identity Provider authenticates the user, and generates a SAML assertion.
Information about the SAML assertion provided by the Identity Provider and associated with the user and the desired target is conveyed from the Identity Provider site to the Service Provider site by the protocol exchange.
Through a sequence of HTTP exchanges, the user browser is transferred to an Assertion Consumer Service (ACS) at the Service Provider site. The WebLogic Server SAML Identity Assertion provider makes up a portion of the ACS.
The Identity Assertion provider maps the identity contained in the assertion to a Subject in the local security realm. The access policies on the requested target are evaluated to determine whether the user is authorized for that target. If access is authorized, the user authenticated by the Identity Provider site is accepted as an authenticated user by the Service Provider site, thereby achieving Web-based SSO.
For more background information about the OASIS SAML standard, see the following:
For SAML V1.1, see Bindings and Profiles for the OASIS Security Assertion Markup Language (SAML) V1.1 (
For SAML V2.0, see:
Profiles for the OASIS Security Assertion Markup Language (SAML) V2.0 (
Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0 (
For information about how SSO with web browsers and HTTP clients is implemented in WebLogic Server, see Single Sign-On with the WebLogic Security Framework.
SSO with Desktop Clients uses HTTP-based authentication with Microsoft clients that have authenticated in the Windows Active Directory environment. The Windows Active Directory environment uses Kerberos as its security protocol. Kerberos provides network authentication of heterogeneous realms. This means a user logged into a Windows domain can access a Web application running on an application server and use their Windows Active Directory credentials to authenticate to the server. The application server can run on any platform that supports Kerberos.
When a Web server receives a request from a browser it can request that the browser use the Kerberos protocol to authenticate itself. This protocol performs authentication via HTTP, and allows the browser (in most cases, Internet Explorer) to pass a delegated credential to allow a web application to log into subsequent Kerberos-based services on the user's behalf.
When an HTTP server wishes to login a Microsoft client, it returns a
401 Unauthorized response to the HTTP request with the
WWW-Authorization:Negotiate header. The browser then contacts the Key Distribution Center (KDC)/Ticket Granting Service (TGS) to obtain a service ticket. It chooses a special Service Principal Name for the ticket request. The returned ticket is then wrapped in a SPNEGO token which is encoded and sent back to the server using an HTTP request. The token is unwrapped and the ticket is authenticated. Once authenticated, the page corresponding to the requested URL is returned.
For information about how SSO with Microsoft clients is implemented in WebLogic Server, see Desktop SSO Process.
Authorization is the process whereby the interactions between users and WebLogic resources are controlled, based on user identity or other information. In WebLogic Server, Authorization providers use concepts of security policies, ContextHandlers, Access Decisions, and so on, to provide authorization. An Authorization provider is used to limit the interactions between users and WebLogic resources to ensure integrity, confidentiality, and availability.
The following sections describe authorization concepts and functionality:
A WebLogic resource is a structured object used to represent an underlying WebLogic Server entity, which can be protected from unauthorized access using security roles and security policies.
WebLogic resources are hierarchical. Therefore, the level at which you define these security roles and security policies is up to you. For example, you can define security roles and security policies on: entire enterprise applications (EARs); an Enterprise JavaBean (EJB) JAR containing multiple EJBs; a particular Enterprise JavaBean (EJB) within that JAR; or a single method within that EJB.
WebLogic resource implementations are available for:
Common Object Model (COM) resources
Enterprise Information System (EIS) resources
Enterprise JavaBean (EJB) resources
Java Database Connectivity (JDBC) resources
Java Messaging Service (JMS) resources
Java Naming and Directory Interface (JNDI) resources
Web application resources
Web service resources
Work Context resources
Each of these WebLogic resource implementations is explained in detail in the Java API Reference for Oracle WebLogic Server.
Security policies replace access control lists (ACLs) and answer the question "Who has access to a WebLogic resource?" A security policy is created when you define an association between a WebLogic resource and one or more users, groups, or security roles.
You can optionally define date and time constraints for a security policy. A WebLogic resource has no protection until you assign it a security policy.
You assign security policies to any of the defined WebLogic resources (for example, an EJB resource or a JNDI resource) or to attributes or operations of a particular instance of a WebLogic resource (an EJB method or a servlet within a Web application). If you assign a security policy to a type of WebLogic resource, all new instances of that resource inherit that security policy. Security policies assigned to individual resources or attributes override security policies assigned to a type of WebLogic resource. For a list of the defined WebLogic resources, see WebLogic Resources.
Security policies are stored in an Authorization provider's database. By default, the XACML Authorization provider is configured in a domain, and security policies are stored in the embedded LDAP server.
To use a user or group to create a security policy, the user or group must be defined in the security provider database for the Authentication provider that is configured in the security realm. To use a security role to create a security policy, the security role must be defined in the security provider database for the Role Mapping provider that is configured in the security realm. By default, the WebLogic Authentication and XACML Role Mapping providers are configured in the database in the embedded LDAP server.
By default, security policies are defined in WebLogic Server for the WebLogic resources. These security policies are based on security roles and default global groups. You also have the option of basing a security policy on a user. Oracle recommends basing security policies on security roles rather than users or groups. Basing security policies on security roles allows you to manage access based on a security role that a user or group is granted, which is a more efficient method of management. For a listing of the default security policies for the WebLogic resources, see Default Root Level Security Policies in Securing Resources Using Roles and Policies for Oracle WebLogic Server.
A ContextHandler is a high-performing WebLogic class that obtains additional context and container-specific information from the resource container, and provides that information to security providers making access or role mapping decisions.
ContextHandler interface provides a way for an internal WebLogic resource container to pass additional information to a WebLogic Security Framework call, so that a security provider can obtain contextual information beyond what is provided by the arguments to a particular method. A ContextHandler is essentially a name/value list and as such, it requires that a security provider know what names to look for. (In other words, use of a ContextHandler requires close cooperation between the WebLogic resource container and the security provider.) Each name/value pair in a ContextHandler is known as a context element, and is represented by a
Currently, three types of WebLogic resource containers pass ContextHandlers to the WebLogic Security Framework: the Servlet, EJB, and Web service containers. Thus, URL (Web), EJB, and Web service resource types have different context elements whose values Adjudication, Identity Assertion, Authorization Credential Mapping, and Role Mapping providers and the LoginModules used by an Authentication provider can inspect. An implementation of the
AuditContext interface (used when a security provider is implemented to post audit events) may also examine the values of context elements.
For more information about the values of particular context elements, see ContextHandlers and WebLogic Resources in Developing Security Providers for Oracle WebLogic Server.
Like LoginModules for Authentication providers, an Access Decision is the component of an Authorization provider that actually answers the "is access allowed?" question.
Specifically, an Access Decision is asked whether a subject has permission to perform a given operation on a WebLogic resource, with specific parameters in an application. Given this information, the Access Decision responds with a result of
Adjudication involves resolving any authorization conflicts that may occur when more than one Authorization provider is configured in a security realm, by weighing the result of each Authorization provider's Access Decision.
In WebLogic Server, an Adjudication provider is used to tally the results that multiple Access Decisions return, and determines the final
DENY decision. An Adjudication provider may also specify what should be done when an answer of
ABSTAIN is returned from a single Authorization provider's Access Decision.
Identity and Trust
WebLogic Server uses private keys, digital certificates, and trusted certificates issues by certification authorities to establish and verify server identity and trust.
The public key is embedded into a digital certificate. A private key and digital certificate provide identity. The trusted certificate authority (CA) certificate establishes trust for a certificate. Certificates and certificate chains need to be validated before a trust relationship is established.
This topic details the concepts associated with identity and trust. See the following topics:
WebLogic Server uses public key encryption technology for authentication.
With public key encryption, a public key and a private key are generated for a server. The keys are related such that data encrypted with the public key can only be decrypted using the corresponding private key and vice versa. The private key is carefully protected so that only the owner can decrypt messages that were encrypted using the public key.
Digital certificates are electronic documents used to verify the unique identities of principals and entities over networks such as the Internet.
A digital certificate securely binds the identity of a user or entity, as verified by a trusted third party (known as a certificate authority), to a particular public key. The combination of the public key and the private key provides a unique identity to the owner of the digital certificate.
Digital certificates enable verification of the claim that a specific public key does in fact belong to a specific user or entity. A recipient of a digital certificate can use the public key in a digital certificate to verify that a digital signature was created with the corresponding private key. If such verification is successful, this chain of reasoning provides assurance that the corresponding private key is held by the subject named in the digital certificate, and that the digital signature was created by that subject.
A digital certificate typically includes a variety of information, such as the following:
The name of the subject (holder, owner) and other information required to confirm the unique identity of the subject, such as the URL of the Web server using the digital certificate, or an individual's e-mail address
The subject's public key
The name of the certificate authority that issued the digital certificate
A serial number
The validity period (or lifetime) of the digital certificate (defined by a start date and an end date)
The most widely accepted format for digital certificates is defined by the ITU-T X.509 international standard. Digital certificates can be read or written by any application complying with the X.509 standard. The public key infrastructure (PKI) in WebLogic Server recognizes digital certificates that comply with X.509 version 3, or X.509v3. Oracle recommends obtaining digital certificates from a certificate authority such as Verisign or Entrust.
See Configuring SSL in Administering Security for Oracle WebLogic Server.
Digital certificates are issued by certificate authorities (CAs).
Any trusted, third-party organization or company that is willing to vouch for the identities of those to whom it issues digital certificates and public keys can be a CA. When a CA creates a digital certificate, the CA signs it with its private key, which ensures that any tampering will be detected. The CA then returns the signed digital certificate to the requesting party.
The requesting party can verify the signature of the issuing CA by using the public key of that CA. The CA makes its public key available by providing a certificate issued from a higher-level certificate authority attesting to the validity of the public key of the lower-level certificate authority. This scheme gives rise to hierarchies of certificate authorities. This hierarchy is terminated by a top-level, self-signed certificate known as the root certificate, because no other public key is needed to certify it.
A root certificate is issued by a trusted (root) CA. A CA certificate that is signed by a higher-level CA is known as an intermediate certificate. The issuer of an intermediate certificate is known as an intermediate CA.
If the recipient has a digital certificate containing the public key of an intermediate CA that is signed by a superior CA who the recipient already trusts, the recipient of an encrypted message can develop trust in the public key of an intermediate CA recursively. In this sense, a digital certificate is a stepping stone in digital trust. Ultimately, it is necessary to trust only the public keys of a small number of top-level CAs. Through a chain of certificates, or certificate path, trust in a large number of users' digital signatures can be established.
The number of certificates in a certificate path is called the certificate path length. The X.509 standard includes a constraint,
pathLenConstraint, that can be specified in a root certificate. When creating a root certificate, a CA can specify this constraint to set a limit on the maximum number of intermediate certificates that may follow that root certificate in a certificate path. In effect, this constraint limits the size of the certificate path length, which is a property of trust that is verified during the SSL handshake.
In summary, digital signatures establish the identities of communicating entities, but a digital signature can be trusted only to the extent that the public key for verifying it can be trusted.
See Configuring SSL in Administering Security for Oracle WebLogic Server.
Certificate Lookup and Validation
In WebLogic Server, certificate validation is performed by the Certificate Lookup and Validation (CLV) framework which completes and validates X.509 certificate chains for inbound 2-way SSL, outbound SSL, application code, and WebLogic Web services.
Applications that rely on public key technology for security must be confident that a user's public key is genuine. A user may have a chain of certificates which recursively point to the trusted CA that issued the initial certificate (referred to as the end certificate). A certificate chain must be validated before it can be used to establish trust. In addition, a user may not have a complete chain from a trusted CA to the target certificate. Completing a valid chain of certificates from the target certificate to the trusted CA is another requirement for public key technology.
The CLV framework receives a certificate or certificate chain, completes the chain (if necessary), and lookups and validates the certificate in the certificate chain. The framework can use the end certificate, the Subject DN, the Issuer DN plus serial number, the subject key identifier and/or X.509 thumbprint to find and validate a certificate chain. In addition, the framework can perform additional validation on the certificate chain such as revocation checking.
The CLV framework is based on the JDK architecture and plug-in framework for locating and validating certificate chains. The CLV providers were built using the JDK CertPath Builder and CertPath Validator API/SPI.
Secure Sockets Layer (SSL)
WebLogic Server fully supports SSL communication, which enables secure communication between applications connected through the internet. WebLogic Server uses the Java Secure Socket Extension (JSSE) as the SSL implementation for securing incoming connections, and also for outgoing connections that use the WebLogic SSL APIs.
Applications hosted on WebLogic Server can also invoke JSSE directly for outbound SSL connections.
As of WebLogic Server version 12.1.1, JSSE is the only SSL implementation that is supported. The Certicom-based SSL implementation is removed and is no longer supported in WebLogic Server.
For complete information about JSSE, see the Java Secure Socket Extension (JSSE) Reference Guide at the following location:
The following topics are discussed in this section:
WebLogic Server provides a pure-Java implementation of SSL. SSL provides a mechanism that communicating applications can use to authenticate each other's identity and the encryption of the data exchanged by applications.
When SSL is used, the target (the server) always authenticates itself to the initiator (the client). Optionally, if the target requests it, the initiator can authenticate itself to the target. Encryption scrambles the data that is transmitted. An SSL connection begins with a handshake during which the applications exchange digital certificates, agree on the encryption algorithms to be used, and generate the encryption keys to be used for the remainder of the session.
SSL provides the following security features:
Server authentication - WebLogic Server uses its digital certificate, issued by a trusted certificate authority, to authenticate to clients. SSL minimally requires the server to authenticate to the client using its digital certificate. If the client is not required to present a digital certificate, the connection type is called one-way SSL authentication.
Client Identity Verification - Optionally, clients might be required to present their digital certificates to WebLogic Server. WebLogic Server then verifies that the digital certificate was issued by a trusted certificate authority and establishes the SSL connection. An SSL connection is not established if the digital certificate is not presented and verified. This type of connection is called two-way SSL authentication, a form of mutual authentication.
Confidentiality - All client requests and server responses are encrypted to maintain the confidentiality of data exchanged over the network.
Data Integrity - Each SSL message contains a message digest computed from the original data. On the receiving end, a new digest is computed from the de-crypted data and then compared with the digest that came with the message. If the data is altered, the digests don't match and tampering is detected.
If you are using a Web browser to communicate with WebLogic Server, you can use the Hyper-Text Transfer Protocol with SSL (HTTPS) to secure network communications.
A cipher suite is a combination of cryptographic parameters that define the security algorithms and key sizes used for authentication, key agreement, encryption, and integrity protection. Cipher suites protect the integrity of a communication.
For example, the cipher suite called
RSA_WITH_RC4_128_MD5 uses RSA for key exchange, RC4 with a 128-bit key for bulk encryption, and MD5 for message digest.
The set of cipher suites supported by the JDK default JSSE provider,
SunJSSE, is available at the following URLs:
- JDK 11:
For information about configuring WebLogic Server to use the JSSE-based SSL implementation, see Using the JSSE-Based SSL Implementation in Administering Security for Oracle WebLogic Server.
WebLogic Server tunnels the HTTP, T3, and IIOP protocols over SSL.
SSL can be used by Web browsers and Java clients as follows:
A Web browser makes an SSL connection to a server over HTTPS. The browser then sends HTTP requests and receives HTTP responses over this SSL connection. For example:
WebLogic Server supports SSL versioning which means it can communicate with any clients over this protocol including Web browsers.
Java clients using HTTP/T3 protocols are tunnelled over SSL. For example:
Java clients running in WebLogic Server can establish either T3S connections to other WebLogic Server instances, or HTTPS connections to other servers that support SSL, such as Web servers or secure proxy servers.
One-way/Two-way SSL Authentication
WebLogic Server supports one-way and two-way SSL authentication.
With one-way SSL authentication, the target (the server) is required to present a digital certificate to the initiator (the client) to prove its identity. The client performs two checks to validate the digital certificate:
The client verifies that the certificate is trusted (meaning, it was issued by the client's trusted CA), is valid (not expired), and satisfies the other certificate constraints.
The client checks that the certificate Subject's common name (CN) field value matches the host name of the server to which the client is trying to connect
If both of the above checks return true, the SSL connection is established.
With two-way SSL authentication, both the client and the server must present digital certificates before the SSL connection is enabled between the two. Thus, in this case, WebLogic Server not only authenticates itself to the client (which is the minimum requirement for certificate authentication), but it also requires authentication from the requesting client. Two-way SSL authentication is useful when you must restrict access to trusted clients only.
Figure 3-3 illustrates WebLogic Server SSL connections and shows which connections support one-way SSL, two-way SSL, or both. The Web browser client, Web Server, Fat client, Web services client, and SSL server connections can be configured for either one-way or two-way SSL. WebLogic Server determines whether an SSL connection is configured for one-way or two-way. Use the WebLogic Server Administration Console to configure SSL.
Figure 3-3 How WebLogic Server Supports SSL Connections
Description of "Figure 3-3 How WebLogic Server Supports SSL Connections"
By default, WebLogic Server is configured for one-way SSL authentication, however, the SSL port is disabled.
Using the WebLogic Server Administration Console, you can configure WebLogic Server for two-way SSL authentication.
To use one-way SSL from a client to a server: enable the SSL port on the server, configure identity for the server and trust for the client.
To use two-way SSL between a client and a server: enable two-way SSL on the server, configure trust for the server, and identity for the server.
In either case, the trusted CA certificates need to include the trusted CA certificate that issued the peer's identity certificate. This certificate does not necessarily have to be the root CA certificate.
To acquire a digital certificate for your server, you generate a public key, private key, and a Certificate Signature Request (CSR), which contains your public key. You send the CSR request to a certificate authority and follow their procedures for obtaining a signed digital certificate.
Once you have your private keys, digital certificates, and any additional trusted CA certificates that you may need, you need to store them so that WebLogic Server can use them to verify identity. Store private keys and certificates in keystores.
To use SSL when connecting to a WebLogic server application with your browser, you simply specify HTTPS and the secure port (port number 7002) in the URL. For example:
localhost is the name of the system hosting the Web application.
Host Name Verification
Host Name verification is the process of verifying that the name of the host to which an SSL connection is made is the intended or authorized party. Host name verification prevents man-in-the-middle attacks when a Web client (a Web browser, a WebLogic client, or a WebLogic Server acting as a client) requests an SSL connection to another application server.
By default, the SSL client, as a function of the SSL handshake, compares the common name in the SubjectDN of the SSL server's digital certificate with the host name of the SSL server to which it is trying to connect. If these names do not match, the SSL connection is dropped.
The Trust Manager provides a way to override the default SSL trust validation rules. It allows the server to decide whether or not it trusts the client that is contacting it. Using a Trust Manager you can perform custom checks before continuing an SSL connection.
For example, you can use the Trust Manager to specify that only users from specific localities, such as towns, states, or countries, or users with other special attributes, can gain access via the SSL connection.
WebLogic Server provides interfaces that allows custom Trust Manager implementations to be called during the SSL handshake. Custom implementations can override the handshake error detected by the SSL implementation validation check, raise an error based on their own certification rules, and control whether outbound SSL uses certificate lookup and validation. See Using a Trust Manager and Using the CertPath Trust Manager in Developing Applications with the WebLogic Security Service.
The Federal Information Processing Standards (FIPS) 140-2 is a standard that describes U.S. Federal government requirements for sensitive but unclassified use. WebLogic Server supports the ability to use a FIPS-compliant (FIPS 140-2) crypto module.
See Enabling FIPS Mode in Administering Security for Oracle WebLogic Server.
A firewall controls network traffic by acting as a barrier between a trusted and an untrusted network. Along with firewalls, you can use WebLogic Server connection filters and perimeter authentication to restrict access to resources based on user and network information.
Firewalls can be a combination of software and hardware, including routers and dedicated gateway machines. They employ filters that allow or disallow traffic to pass based on the protocol, the service requested, routing information, and the origin and destination hosts or networks. They may also allow access for authenticated users.
Figure 3-4 illustrates a typical setup with a firewall that filters traffic destined for a WebLogic Server cluster.
Figure 3-4 Typical Firewall Setup
Description of "Figure 3-4 Typical Firewall Setup"
You can use the following features in WebLogic Server in conjunction with firewalls:
You can use WebLogic Server connection filters to set up firewalls that filter network traffic based on protocols, IP addresses, and DNS node names. See Using Network Connection Filters in Developing Applications with the WebLogic Security Service.
You can use Identity Assertion providers to set up perimeter authentication - a special type of authentication using tokens. The WebLogic Server security architecture supports Identity Assertion providers that perform perimeter-based authentication (Web server, firewall, VPN) and handle multiple security token types/protocols (SOAP, SAML, SPNEGO, IIOP-CSIv2).
Java EE and WebLogic Security
WebLogic Server utilizes the security services of the JDK for implementing and using user authentication and authorization. WebLogic Server supports Java SE and Java EE security packages, and also provides support for the EJB interoperability protocol.
The Java EE security services are based on standardized, modular components. WebLogic Server implements these Java security service methods according to the standard, and adds extensions that handle many details of application behavior automatically, without requiring additional programming.
WebLogic Server's support for Java security means that application developers can take advantage of the latest enhancements and developments in the area of security, thus leveraging a company's investment in Java programming expertise. By following the defined and documented Java standard, WebLogic Server's security support has a common baseline for Java developers.
The following topics are discussed in this section:
Java Security Packages
WebLogic Server is compliant with and supports the following Java SE and Java EE 8.0 security packages:
The Java Secure Socket Extension (JSSE)
JSSE is a set of packages that support and implement the SSL and TLS v1 protocol, making those protocols and capabilities programmatically available. WebLogic Server provides Secure Sockets Layer (SSL) support for encrypting data transmitted across WebLogic Server clients, as well as other servers.
Java Authentication and Authorization Services (JAAS)
JAAS is a set of packages that provide a framework for user-based authentication and access control. WebLogic Server uses only the authentication classes of JAAS.
There are security configuration settings in a WebLogic Server domain that can impact the use of JAAS authorization if needed in your environment. See Configuring a Domain to Use JAAS Authorization in Administering Security for Oracle WebLogic Server for more information about when you might need to do this.
JAAS is used as follows:
For remote Java client authentication
For authentication internally in instances of WebLogic Server in the Web and EJB containers and in the WebLogic Authentication and Identity Assertion providers.
For more information on JAAS, see Java Authentication and Authorization Service (JAAS).
The Java Security Manager
The Java Security Manager is the security manager for the Java Virtual Machine (JVM). The security manager works with the Java API to define security boundaries through the
java.lang.SecurityManager class. The
SecurityManager class enables programmers to establish a custom security policy for their Java applications.
The Java Security Manager can be used with WebLogic Server to provide additional protection for WebLogic resources running in the JVM. Use of the Java Security Manager to protect WebLogic resources in WebLogic Server is an optional security step.
You can use the Java Security Manager to perform the following security tasks to protect WebLogic resources:
weblogic.policyfile for general use.
Set application-type security policies on EJBs and Resource Adapters.
You use the Java security policy file to perform this task.
Set application-specific security policies on specific EJBs and Resource Adapters.
You use the deployment descriptors (
rar.xml) to perform this task.
For more information on how to use the Java Security Manager to perform these tasks, see Using Java Security to Protect WebLogic Resources in Developing Applications with the WebLogic Security Service.
Java Cryptography Architecture and Java Cryptography Extensions (JCE)
These security APIs provide a framework for accessing and developing cryptographic functionality for the Java platform and developing implementations for encryption, key generation and key agreement, and Message Authentication Code (MAC) algorithms.
WebLogic Server fully supports these security APIs.
Java Authorization Contract for Containers (JACC)
JACC provides an alternate authorization mechanism for the EJB and Servlet containers in a WebLogic Server domain. When JACC is configured, the WebLogic Security Framework access decisions, adjudication, and role mapping functions are not used for EJB and Servlet authorization decisions. The JACC classes are used for role-to-principal mapping as well as for rendering access decisions. You cannot use the JACC framework in conjunction with the WebLogic Security Framework. The JACC classes used by WebLogic Server do not include an implementation of a Policy object for rendering decisions but instead rely on the Java
Java Authentication Service Provider Interface for Containers (JASPIC)
The Java Authentication Service Provider Interface for Containers (JASPIC) specification (
http://www.jcp.org/en/jsr/detail?id=196) defines a service provider interface (SPI) by which authentication providers that implement message authentication mechanisms can be integrated in server Web application message processing containers or runtimes.
You do not have to modify your Web application code to use JASPIC. Instead, you use the WebLogic Server Administration console or WLST to enable JASPIC for the Web application post deployment.
For more information on how to use JASPIC with a Web application, including how to custom validate principals created by the SAM, see Using JASPIC for a Web Application in Developing Applications with the WebLogic Security Service.
Java EE Security API (JSR 375)
The JSR 375 Java EE Security API specification (
https://www.jcp.org/en/jsr/detail?id=375) defines portable, plug-in interfaces for authentication and identity stores, and an injectable
SecurityContext interface that provides an access point for programmatic security. You can use the built-in implementations of the plug-in SPIs, or write custom implementations.
In WebLogic Server, these authentication mechanisms are supported in the Web application container, including web services, and the
SecurityContext interfaces are supported in the Servlet and EJB containers.
For details about how to use the Java EE Security API with WebLogic Server, see Using the Java EE Security API in Developing Applications with the WebLogic Security Service.
Common Secure Interoperability Version 2 (CSIv2)
WebLogic Server provides support for the Enterprise JavaBean (EJB) interoperability protocol that is based on Internet Inter-ORB (IIOP) (GIOP version 1.2) and the CORBA Common Secure Interoperability version 2 (CSIv2) specification. CSIv2 support in WebLogic Server:
Interoperates with the Java Platform, Enterprise Edition (J2EE) reference implementation.
Allows WebLogic Server IIOP clients to specify a username and password in the same manner as T3 clients.
Supports Generic Security Services Application Programming Interface (GSSAPI) initial context tokens. For this release, only usernames and passwords and GSSUP (Generic Security Services Username Password) tokens are supported.
The CSIv2 implementation in WebLogic Server passed Java EE Compatibility Test Suite (CTS) conformance testing.
The external interface to the CSIv2 implementation is a JAAS LoginModule that retrieves the username and password of the CORBA object. The JAAS LoginModule can be used in a WebLogic Java client or in a WebLogic Server instance that acts as a client to another Java EE application server. The JAAS LoginModule for the CSIv2 support is called
UsernamePasswordLoginModule, and is located in the
For information related to load balancing support for CSIv2 in a WebLogic Server cluster, see Server Affinity and IIOP Client Authentication Using CSIv2 in Administering Clusters for Oracle WebLogic Server
WebLogic Server extends support for using JASPIC to configure an Authentication Configuration Provider for a Web application and using that instead of the default WLS authentication mechanism for that Web application.
The Java Authentication Service Provider Interface for Containers (JASPIC) specification (
http://www.jcp.org/en/jsr/detail?id=196) defines a service provider interface (SPI) by which authentication providers that implement message authentication mechanisms can be integrated in server Web application message processing containers or runtimes.
WebLogic Server allows you to use JASPIC to delegate authentication for Web applications to your configured Authentication Configuration Providers.
This section describes the following topics:
Overview of Java Authentication Service Provider Interface for Containers (JASPIC)
The JASPIC Authentication Configuration Provider assumes responsibility for authenticating the user credentials for a Web application and returning a Subject. It authenticates incoming Web application messages and returns the identity (the expected Subject) established as a result of the message authentication to WebLogic Server. This means that if you configure an Authentication Configuration Provider for a Web application, it is used instead of the WLS authentication mechanism for that Web application.
You can use either your own Server Authentication Module (SAM) that works with the default WebLogic Server Authentication Configuration Provider, or you can create and use both your own Authentication Configuration Provider and SAM.
As described in the Java Authentication Service Provider Interface for Containers (JASPIC) specification (
http://www.jcp.org/en/jsr/detail?id=196), the Authentication Configuration Provider (called "authentication context configuration provider" in the specification) is an implementation of the
javax.security.auth.message.config.AuthConfigProvider interface. The Authentication Configuration Provider provides a configuration mechanism used to define the registered SAM's and bindings to applications that require protection from unauthenticated/authorized access.
WebLogic Server supports only JASPIC 1.1. WebLogic Server supports only the Servlet Profile.
The SAM represents the implementation of a server-side authentication module that is JASPIC compliant. As described in the Java Authentication Service Provider Interface for Containers (JASPIC) specification (
http://www.jcp.org/en/jsr/detail?id=196), a SAM implements the
javax.security.auth.message.module.ServerAuthModule interface and is invoked by WebLogic Server at predetermined points in the message processing model.
WebLogic Server allows you to:
Enable or disable JASPIC across an entire domain. Only when JASPIC is enabled for the domain can you then decide how each Web application supports JASPIC.
If you disable JASPIC for the domain, JASPIC is disabled for all Web applications, regardless of their configuration.
Configure domain-wide WebLogic Authentication Configuration Providers, for which you specify the class name and properties of your own Server Authentication Module (SAM).
Configure domain-wide Custom Authentication Providers, for which you specify the class name of this provider and its properties.
For each of your deployed Web applications in the domain, determine whether you want JASPIC to be disabled (the default), or select one of your configured Authentication Configuration Providers to authenticate the user credentials and return a valid Subject.
JASPIC Programming Model
The JASPIC programming model is described in the Java Authentication Service Provider Interface for Containers (JASPIC) specification (
A sample SAM implementation is described in Adding Authentication Mechanisms to the Servlet Container in the GlassFish Server Open Source Edition Application Development Guide. Although written from the GlassFish Server perspective, the tips for writing a SAM, and the sample SAM itself, are instructive.
Java EE Security API
Oracle WebLogic Server supports the Java EE Security API (JSR 375) which defines portable authentication mechanisms (such as
IdentityStore), and an access point for programmatic security using the
SecurityContext interface. In WebLogic Server, these authentication mechanisms are supported in the web container, and the
SecurityContext interfaces are supported in the Servlet and EJB containers.
The portable, plug-in authentication and identity store interfaces provide an advantage over standard, container-provided implementations because they allow the application to control the authentication process and the identity stores used for that authentication in a standard and portable way. Bundling the security configuration in the application, instead of configuring it externally, improves the management of the application’s lifecycle, especially in a world of microservices that are distributed in containers.
The Java EE Security API requires that group principal names are mapped to roles of the same name by default. In WebLogic Server, if the
security-role-assignment element in the
weblogic.xml deployment descriptor does not declare a mapping between a security role and one or more principals in the WebLogic Server security realm, then the role name is used as the default principal.
There are no special logging requirements. Audit events triggered by implementations of the Java EE Security API are logged by the WebLogic Auditing Provider, if configured.
The programming model for the Java EE Security API 1.0 (JSR 375) is defined in the specification at
For details about using JSR 375 in WebLogic Server, see Using the Java EE Security API in Developing Applications with the WebLogic Security Service.
WebLogic Server supports the following JSR 375 plug-in SPIs for authentication:
HttpAuthenticationMechanism(HAM) - This interface is used to authenticate callers to a web application. An application can supply its own custom
HttpAuthenticationMechanism, or use one of the built-in mechanisms provided by the container. WebLogic Server supports the three standard built-in authentication mechanisms that support BASIC, FORM, and Custom FORM authentication, as well as the custom HAM. The
HttpAuthenticationMechanisminterface is designed to capitalize on the strengths of existing Servlet and JASPIC authentication mechanisms, and requires that JASPIC is enabled in WebLogic Server (the default).
IdentityStore- This interface defines methods for validating a caller’s credentials (such as user name and password) and returning group membership information. An application can provide its own custom
IdentityStore, or use the built-in LDAP or Database store included in WebLogic Server.
RememberMeIdentityStore- This interface is a variation of the
IdentityStoreinterface which is intended to address cases where an authenticated user’s identity should be remembered for an extended period of time so that the caller can return to the application periodically without needing to present primary authentication credentials each time.
Implementations of these SPI interfaces are CDI beans. As such, applications can provide implementations that support application-specific authentication mechanisms, or validate user credentials against application-specific identity stores simply by including the interfaces in a bean archive that is part of the deployed application. For information about CDI support in WebLogic Server, see Using Contexts and Dependency Injection for the Java EE Platform in Developing Applications for Oracle WebLogic Server.
The container is responsible for placing the
HttpAuthenticationMechanism into service. The
IdentityStore interface is intended primarily for use by
HttpAuthenticationMechanism implementations, but could in theory be used by other types of authentication mechanisms (such as a JASPIC
HttpAuthenticationMechanism implementations are not required to use
IdentityStore — they can authenticate users in any manner they choose — but the
IdentityStore interface is a useful and convenient mechanism.
The Java EE Security API (JSR 375) specification defines the
SecurityContext API for use by application code to query and interact with the current security context.
SecurityContext interface defines methods that allow an application to access security information about a caller, authenticate a caller, and authorize a caller. These methods include:
getCallerPrincipal()- Retrieves the Principal representing the caller.
getPrincipalsByType()- Retrieves all principals of the given type.
isCallerInRole()- Checks if the authenticated caller is included in the specified logical application "role".
hasAccessToWebResource()- Determines if the caller has access to the specified web resource for the specified HTTP methods, as determined by the security constraints configured for the application.
authenticate()- Allows an application to signal to the container that it should start the authentication process with the caller.
isCallerInRole() methods are available in the WebLogic Servlet (including Web service) and EJB containers.
hasAccessToWebResource() and the
authenticate() APIs are supported only in the WebLogic Servlet container (including Web service).