Attachment J.2a Judiciary IDAM Requirements Checklist.pdf
PDF 77 KB Posted
- Attached to
- Enterprise Training Software BPA
- Solicitation number
- USCA25Q0045
- Issued by
-
Administrative Office of the U.S. Courts
About this file
This document is a technical requirements specification for an application or SaaS solution's identity infrastructure integration with the Judiciary's systems. The requirements are detailed across five key areas: SAML 2.0 Support, User Provisioning and SCIM, Active Directory Integration, Authentication Restrictions, and Documentation and Support. Critical technical specifications include full SAML 2.0 support with SP-initiated/IdP-initiated SSO, support for standard SAML bindings, metadata processing, security features like assertion signing and encryption, SCIM 2.0 user provisioning capabilities, and Active Directory integration methods including LDAPS, Kerberos, and standard AD authentication attributes. The document emphasizes the need for flexible, standards-based identity protocols, with specific requirements for authentication methods, group access control, hybrid authentication support, and comprehensive vendor documentation and integration resources.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| USCA25Q0045 0004.pdf | ||
| Attachment J.1 SOW Amend 0003.pdf | ||
| USCA25Q0045 Amend 0003.pdf | ||
| Attachment J.2a Judiciary IDAM Requirements Checklist Amend 0003.pdf | ||
| Attachment J.2 Requirements Questionnaire Amend 0003.xlsx | XLSX spreadsheet | |
| USCA25Q0045 Enterprise Training BPA Q and A Updated 10-3.xlsx | XLSX spreadsheet | |
| USCA25Q0045 Enterprise Training BPA Q and A Updated.xlsx | XLSX spreadsheet | |
| Attachment J.2 Requirements Questionnaire Amd 0002.xlsx | XLSX spreadsheet | |
| Attachment J.1 SOW Amd 0002.pdf | ||
| Attachment J.3 Training Platform Price Workbook Amd 0002.xlsx | XLSX spreadsheet | |
| USCA25Q0045 Amd 0002.pdf | ||
| USCA25Q0045 Enterprise Training BPA Q and A.xlsx | XLSX spreadsheet | |
| USCA25Q0045 0001 Due Date Extension.pdf | ||
| Attachment J.1 SOW.pdf | ||
| Attachment J.2 Requirements Questionnaire.xlsx | XLSX spreadsheet | |
| Attachment J.3 Training Platform Price Workbook.xlsx | XLSX spreadsheet | |
| RFQ USCA25Q0045.pdf |
Show all 17
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
To ensure compatibility with the Judiciary's identity infrastructure, the application or SaaS solution shall comply with the following technical requirements. This would ensure seamless integration with our standards-based Identity Provider and provisioning system without requiring proprietary workarounds.
1. SAML 2.0 Support The solution must:
o Fully support SAML 2.0 as a Service Provider (SP), including SP-initiated and IdP-initiated SSO.
o Support standard SAML bindings, including HTTP-Redirect and HTTP-POST.
o Accept and process SAML metadata (upload and download).
o Support RelayState for deep linking.
o Allow multiple NameID formats (e.g., emailAddress, persistent).
o Support custom attribute mappings and the processing of attributes in the assertion.
o Support standard security features including:
Assertion signing, message encryption, and SHA-256 or higher hashing.
Certificate upload and rotation.
o Provide access to detailed SAML request/response logs and clear error logging.
o Support multi-tenant or federated deployments.
o Provide test IdP metadata or a sandbox for integration.
o Support OpenID Connect (OIDC) if SAML is unavailable.
2. User Provisioning and SCIM
The solution must:
o Indicate whether account provisioning is required.
o Support SCIM 2.0 for provisioning and deprovisioning users.
o Support schema extensions for custom attributes.
o Allow for group provisioning, role-based access management, and permissions control.
o Support automatic deprovisioning (e.g., upon user departure).
o Support PATCH operations for incremental updates.
o Provide documented APIs and payload samples for SCIM endpoints.
o Support OAuth 2.0 or comparable authentication methods for SCIM.
o Provide access to event logs related to provisioning activities.
o Provide a sandbox or test environment for integration validation.
o Supply SCIM-specific documentation and example payloads.
3. Active Directory Integration
In order to support NAD for federated authentication or provisioning the solution must support:
o Supported authentication method
LDAPS (bind), Kerberos, or custom appliance.
Authenticate users using standard AD attributes (e.g., sAMAccountName, userPrincipalName).
Support group-based access control leveraging existing AD group structures.
ADFS is supported for national system on a case-by-case basis.
o Supported provisioning method LDAPS or custom appliance o Clearly define any required AD schema extensions or custom attributes.
o Future proofing Support hybrid authentication (AD + cloud IdP).
Offer flexibility to transition from AD-based authentication to SAML or OIDC in the future.
4. Cloud only authentication (cloud IdP) is not supported
5. Documentation and Support Vendor must be able to provide:
o Detailed integration documentation including SAML, SCIM, and AD configurations.
o Sample payloads, schemas, and setup instructions.
o Support resources with experience in standards-based identity protocols.
File details come from the government source that posted it. Updated .