What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

Currently, in Atlas UI federation (SAML), request certificates are signed using RSA-SHA256; however, the digest algorithm is always SHA1.

What would you like to see happen?

Describe the desired outcome or enhancement.

Enable support for configuring SHA256 as the digest algorithm for SAML AuthnRequest signatures, in addition to the current SHA1 default. Once available, update defaults to use SHA256 for both signature and digest algorithms.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

This aligns with modern security standards and upcoming Okta GA support for SHA256 digest configuration. Configuring digest algorithm in Okta is now in early access.

What steps, if any, are you taking today to manage this problem?