IssueTracker

This will create a public issue which anybody can view and comment on.

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:
Hi, I think we have to escalate this one more. Because according to our SSO identity provider "The message is not signed with expected signature algorithm". As far as I understand there is a signing process on identity provider side and there is the same process on service provider side. And in case of google identity provider its a SHA1. Currently to make SSO working our idp have to set it to SHA1, but it has to be SHA256 because SHA1 is outdated and dangerous.

What you expected to happen:
Ability to change signing algorithm in google cloud identity platform provider settings.

Steps to reproduce:
Create provider in identity platform and try to login with it to SSO (in our client case its a microsoft ADFS) with firebase app.

Other information (workarounds you have tried, documentation consulted, etc):
I've created an issue before, but probably because it was closed once no one was looking into my reply https://issuetracker.google.com/issues/188864831