SAML Assertion Request for Custom Okta Identity Provider Displays Digest Value as SHA1
Last Updated:
Overview
When viewing the request assertion for a custom-defined Security Assertion Markup Language (SAML) Identity Provider (IdP) set to sign authentication requests with the SHA-256 algorithm, the Digest Algorithm parameter displays as SHA1. This occurs because the "Digest Value" is not a configurable parameter on the Okta IdP page and automatically defaults to SHA1. Administrators cannot configure the "Digest Value" parameter in the Okta IdP configuration.
Review the following image for an example of the Digest Algorithm parameter displaying as SHA1.
Applies To
- Security Assertion Markup Language (SAML)
- Identity Provider (IDP)
- SHA1
- SHA-256
- Single Sign On (SSO)
- Okta Classic Engine
- Okta Identity Engine (OIE)
Cause
The "Digest Value" is not a configurable parameter on the IdP page and gets added automatically with the default value, which is SHA1.
Solution
Why does the Digest Algorithm display as SHA1?
The "Digest Value" parameter is not configurable in the Okta IdP configuration. Okta automatically sets the default value to SHA1.
