Oracle OpenSSO Fedlet

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	The Oracle OpenSSO Fedlet (Fedlet) is a compact Security Assertion Markup Language service provider implementation. The product establishes single sign-on (SSO) between an identity provider instance and the service provider application without requiring a fully-featured federation product on the service provider side. This product is no longer supported by Oracle. Users should leverage the Oracle Access Manager that contains the functionality set forth in this product.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v20.5
Decision Date:	05/18/2020 at 11:55:37 UTC
Aliases:	Fedlet
Introduced By:	TRM Request
Vendor Name:	Oracle

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
11g		12/31/2010

Current Decision Matrix (05/14/2020)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Release	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4
<Past	CY2016				CY2017				CY2018				Future>
11g	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved
Note:	At the time of writing, version 11.1.1.3.0 is the most recent version released which has reached its end of life.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Security Identity and Access Management	Authentication

Operating Systems Supported by the Technology

Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

WebLogic Server

Comparable Technologies:

Auth0

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This application may improve productivity for specific staff whose responsibilities include establishing single sign-on (SSO) capabilities.

Adoption Risks

This product reached its end of life in 2010. The functionality for this product is embedded in the Oracle Access Manager.
The technology may collect, store or transmit Personally Identifiable Information (PII) or Protected Health Information (PHI).
There is limited support for this technology.
There has been no recent development on this technology, as this product has reached its end of life.
This application relies on Oracle Java Standard Edition (SE) Development Kit which has a rapid patch schedule.
There is no evidence that the Oracle IAM Suite+ itself is Federal Information Processing Standards (FIPS) 140-2 certified; however, the vendor states that "identity federation and the middleware identity and access solutions all sit on the WebLogic Server which is FIPS 140-2 compliant and approved on the VA Technical Reference Model (TRM).
Oracle Identity and Access Management Suite+ is a powerful tool that should be carefully integrated, configured, and monitored. The implementation can be complex due to multiple and interrelated components as it features a web server, database, and service-oriented architecture (SOA). Failure to secure the identity management services and its associated components could potentially result in unauthorized access, the disclosure or potential exposure of VA sensitive data.
There are other VA-approved comparable identity management solutions, and the adoption of this technology could duplicate functionality and create compatibility issues.
All the components in the suite are standalone technology that have been integrated into the Oracle IAM Suite+.
There are more than 10 individual sub-projects currently in development within Oracle IAM Suite+. Each project is independently maintained and may have vastly different security needs compared with other projects within the common environment.
Many of the components in the Suite, such as OpenSSO STS/Fedlet do not have a 12c version because they were not planned for the 12c versions. They are being dropped in favor of Oracle Unified Directory (OUD) which comprised of OVD/DSEE, and OAM.
Components of this suite could run on multiple Oracle and non-Oracle platforms and databases on premise or in the cloud.
For secure WebLogic Server connection, Oracle recommends that administrators enable the administration port in a production environment. The administration port is a special secure port that all WebLogic Server instances in a WebLogic domain can use for administration traffic. By default, this port is not enabled.
There are published vulnerabilities that affect components of this software:
- Oracle Identity Federation, version 11.1.2.2 was affected by CVE-2016-0404.
- Oracle Access Manager, version 11.1.2.3.0 and 12.2.1.3.0 wereaffected by CVE-2018-2879.

Architectural Risks

This technology is not portable, as it only runs on Windows platforms.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/14/2020)

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/14/2020)

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Risks

EMAIL UPDATES