SOURCES SOUGHT
70 -- LDAP Directory Services Product
- Notice Date
- 7/27/2011
- Notice Type
- Sources Sought
- NAICS
- 511210
— Software Publishers
- Contracting Office
- Department of the Treasury, Bureau of the Public Debt (BPD), Division of Procurement, Avery 5F, 200 Third Street, Parkersburg, West Virginia, 26106-5312, United States
- ZIP Code
- 26106-5312
- Solicitation Number
- RFI-BPD-11-0069
- Archive Date
- 7/27/2012
- Point of Contact
- GB/BJ, Fax: 304-480-7203
- E-Mail Address
-
psb3@bpd.treas.gov
(psb3@bpd.treas.gov)
- Small Business Set-Aside
- N/A
- Description
- Purpose The purpose of this Request for Information (RFI) is for market research to survey the commercial marketplace for potential alternate LDAP-based COTS solutions to replace the Bureau of the Public Debt's (BPD's) current LDAP directory services product. Background Since 1997, BPD has provided a full range of Enterprise Level Directory Services to other Federal agencies. BPD's directory services include: • LDAP-based repository for PKI information. • LDAP-based authentication for LDAP-enabled applications. • Real-time replication to our contingency sites. • Load balanced and highly available 24x7x365 Directory Services. The Bureau of Public Debt is a GSA approved Shared Service Provider (SSP) for Public Key Infrastructure (PKI), operating the program on behalf of the Department of the Treasury. The system being sought will support BPD in providing LDAP-based Directory Services to Treasury and multiple non-Treasury franchise customers. Currently this system supports over 40% of all certificates issued to Non-DOD Government Entities. Requirement BPD is evaluating current LDAP-based directory service products that are comprised of both a Directory Server and a Directory Proxy Server. The focus is to take advantage of advancements in technology while benefiting from competitive industry trends. The overall goal is to deploy a system that is designed on, and embeds the latest technology and provides user satisfaction while elevating the proficiency of mission accomplishments. In addition, the ideal system will be designed to accommodate technology infusion in a seamless and cost effective manner, while providing a high level of granularity in its security controls. BPD currently utilizes Oracle Directory Server Enterprise Edition version 6.3.1.1, directory server and directory proxy server. This Directory Service has been in place since 1997 and is the infrastructure supporting well over 100 Treasury applications, including the Department of the Treasury's Personal Identity Verification (PIV) program. Basic system needs for the Directory Server are as follows: • The directory services product must be supported on Oracle Solaris 10 SPARC, and Oracle Solaris 10 x86 / x64 operating systems. • The directory services product must be a LDAP-based directory server, not X.500. • The ability to do real-time replication between a large number of read / write "master" directory servers. • The ability to do filtered replication between directory masters, making it possible to replicate a specific set of attributes so that one writeable master can have a superset of attributes compared to another writeable master server in the same replication topology. • Must be able to keep track of configuration changes made to any directory server, and easily apply the same changes across multiple directory servers in the environment. • The ability to create "filtered" logs for troubleshooting on the fly. This would be able, for example, to separate out a specific client's IP that is having issues, into its own log to make troubleshooting with the customer more efficient. • Have the ability to easily track connections through the infrastructure from the clients, through the LDAP proxy servers and to the directory servers in the log files. • Be able to show the last login time / date for users in the LDAP directory. Basic system needs for the directory proxy server are as follows: • The directory proxy product must be supported to run on Oracle Solaris 10 SPARC, and Oracle Solaris 10 x86 / x64 operating systems. • Provide high availability and load balancing between multiple backend instances of directory servers. • Be able to do "content based routing" to route connections for a specific LDAP suffix to the appropriate backend directory server. • Be able to keep track of configuration changes made to any directory proxy server, and easily apply the same changes across multiple directory proxy servers in the environment. • Ability to pass through information about clients to the backend LDAP directories such as IP address, so that access rules on the directory server can be used to grant access based on IP or subnet. • Be able to filter the results returned to clients by the clients' IP subnets and or bind dn's and or LDAP groups. The filters must be granular enough to send only specified attributes, or block specified attributes to different network subnets and or bind dn's and or LDAP groups. • Be able to create "filtered" logs for troubleshooting on the fly. This would be able, for example, to separate out a specific client's IP that is having issues, into its own log to make troubleshooting with the customer more efficient. Respondents are encouraged to provide product information and offer approaches that merit further consideration. Interested parties should provide a capabilities package to include: • The name and location of your company and contact information. Please ensure contact information includes the name of the point of contact, email address, and telephone number should the Government have questions regarding individual responses. • Product descriptions/specifications that fully describe operational functionality and infrastructure requirements, to include concepts for deployment, performance tuning, product migration, administrator training, etc. • Prior/current experience providing Directory Services Products to federal agencies within the last three years, including contract number, organization supported, whether performance was as a prime or subcontractor, total contract value and a Government point of contact with current telephone number and email address. All responses will be evaluated for merit and technical feasibility. Additional information including demos and or trial license software may be requested to support an ongoing requirement analysis which will incorporate findings and recommendations for a cost effective, user-friendly and highly-productive system. All questions, inquiries and responses must be in writing. Telephone inquiries will not be accepted. This notice does not restrict the Government to an ultimate acquisition approach. All firms responding to this sources sought notice are advised their response is not a submission that will be considered for contract award. All interested parties will be required to respond to any resultant solicitation separately from their response to this sources sought notice. Responses to this request must be submitted no later than 2:00 p.m. ET on August 12, 2011. The following file extensions are not allowable, and application materials/data submitted with these extensions cannot be considered:.bat,.cmd,.com,.exe,.pif,.rar,.scr,.vbs,.hta,.cpl, and.zip files. Microsoft Office compatible and PDF documents are acceptable. PLEASE NOTE: Any future solicitation resulting from this requirement will NOT reference this Request for Information. Responses to this request must be emailed to psb3@bpd.treas.gov - Attention: RFI-BPD-11-0069, GB/BJ.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/TREAS/BPD/DP/RFI-BPD-11-0069/listing.html)
- Place of Performance
- Address: 200 Third Street, Parkersburg, West Virginia, 26101, United States
- Zip Code: 26101
- Zip Code: 26101
- Record
- SN02512797-W 20110729/110727235554-962d1d4c5793cfc8c36d23516e92a4c4 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |