Solutions
ForgeRock Identity Platform
Does not apply to Identity Cloud
400 response when adding or updating resources via REST or Amster when the resource name contains forward slashes in AM (All versions)
The purpose of this article is to provide assistance if you receive a 400 Bad Request response when adding or updating resources via REST or Amster when the resource name contains URL encoded forward slashes. This issue only occurs if AM is deployed in the Apache Tomcat™ web application container and affects resources such as SAML2 entities, policy names and application names.