This issue was migrated from Pagure Issue #3051.Originally filed by vakwetu on 2018-08-17
Recently we had a case where getCRL was being called (from IPA in an openstack context) without an op=X parameter. This results in a 200 return code with an error message provided in the returned message.
This is confusing, and led to a lot of needless debugging.
What should happen is :
The servlet should return a 40x error code
Information should be written in the debug log
Do we even need this op=X parameter?
Alternatively, a RESTful alternative should be provided that behaves properly, and IPA should use this instead in their rewrite rules.
This issue was migrated from Pagure Issue #3051.Originally filed by vakwetu on 2018-08-17
Recently we had a case where getCRL was being called (from IPA in an openstack context) without an op=X parameter. This results in a 200 return code with an error message provided in the returned message.
This is confusing, and led to a lot of needless debugging.
What should happen is :
Alternatively, a RESTful alternative should be provided that behaves properly, and IPA should use this instead in their rewrite rules.