It sounds like you might be trying to add this as a permissions policy (where the principal element is not allowed) instead of as the trust policy (where it is). Try adding this as your trust policy instead.
Problem solved. The documentation is old and misleading. If you create a role for SAML provider via IAM Console, automatically it has trust relationship built in there. So, just permissions need to be added.
My Step Function user role is giving an error for an AWS tutorial I am following.asked 6 months ago
deny access to a specific idp provider while creating an iam roleasked 5 months ago
Policy Condition for federated usersasked 5 months ago
My IAM role is not listed when trying to create a new EC2 instanceasked 10 months ago
Permission boundary on IAM role trust policyasked 6 months ago
Verify permissions for the IAM roleasked 8 months ago
Principals in AWS S3 resource based policy - misleading docs.asked 6 months ago
Misleading AWS doc: can't create Policy for SAML's roleasked 4 years ago
Access Control in Secrets Manager for Federated Usersasked 10 months ago
Is it possible to assign MFA for AWS IAM role?asked 10 months ago