Because of complexities in deployments between Identity and Repose, we want to take an approach to updating that allows rollback of Repose and Identity independently.
We still have a perspective that, long term, we will only support YAML format for attribute mapping policies. However even in this world we may support different media types:
text/yaml;attribMapVersion=1 text/yaml;attribMapVersion=2 as an example.
We want to disable older formats without an update to repose if possible.
- Only formats that the attribute mapper supports will be accepted.
- For each supported format:
- Repose will allow / validate polices in that format but will reject other content types.
- When retrieving a policy from Identity, Repose must send accept headers for each supported format: application/json, application/xml, text/yaml. Identity will send a content type of (application/json) or (text/yaml) and repose will parse the policy based on the content-type. Fail if an unsupported type is sent.