1ecfh (1ecfh) asked a question.
Hello,
I am setting up an app using okta's WS-FED template. I am running into an issue where there app is using SHA-1. My app doesn't allow SHA-1 validation due to its depreciation. How can I upgrade my digital signature to SHA-256?
Hello Gordon,
This is expected for the current WS-FED Template. Depending on the service you are trying to connect to, for example ADFS, you can use a SAML application as it supports the respective flow. Here is an example guide: https://auth0.com/docs/protocols/saml/adfs
What I would recommend is to submit an Idea on our Community page, there is one currently related that would add a GUI option for the Upgrade:
https://support.okta.com/help/s/idea/0872A000000QUITQA4/detail
Another possible solution is to use the Okta API to change it from SHA1 to SHA256.
https://developer.okta.com/docs/how-to/updating_saml_cert
I hope this helps.
Bogdan Andrisan,
Okta Customer Support
Hello Gordon,
Thanks for posting your inquiry in Okta Community Portal.
If you receive a great answer to your question(s), please help readers find it by marking it the best answer. Hover over the answer and click "Best Answer."
Thank you,
Mike Davie
Okta Help Center
Hi,
We also saw the same issue. However, when I followed the step to generate a new SHA256 certificate and use it for the application, the template still use rsa-sha1 for the SignatureMethod in the metadata.xml file. It is possibly hard coded somewhere. That would make this solution not usable. Could you please fix this issue as it affects our application's security?
We are running into this same issue. Has anyone found a way to change the algorithm on what is used to sign the token?
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
Hello Gordon,
This is expected for the current WS-FED Template. Depending on the service you are trying to connect to, for example ADFS, you can use a SAML application as it supports the respective flow. Here is an example guide: https://auth0.com/docs/protocols/saml/adfs
What I would recommend is to submit an Idea on our Community page, there is one currently related that would add a GUI option for the Upgrade:
https://support.okta.com/help/s/idea/0872A000000QUITQA4/detail
Another possible solution is to use the Okta API to change it from SHA1 to SHA256.
https://developer.okta.com/docs/how-to/updating_saml_cert
I hope this helps.
Bogdan Andrisan,
Okta Customer Support