Got 405 response to adding a service pool request when Kerberized

[ijokarumawak]

When I tried to import service definitions from Ambari URL, SAM responded with "405 HTTP method POST is not supported by this URL".

The target URL is http://hdf0:7777/api/v1/catalog/cluster/import/ambari/verify/url After disabling Kerberos, I was able to create a service pool by importing from Ambari, and the target URL was the same one.

While the cluster was Kerberized, I was using streamline.service.keytab and logged in as 'streamline-hdf' user, who has admin role. Why does SAM respond with 405 when it is Kerberized?

[ijokarumawak]

It seems the same issue had happened with Schema Registry and the problematic error page mapping to 401.html is removed from Schema Registry. hortonworks/registry#378

In a Kerberized HDF environment, Schema Registry non-GET requests work fine. But non-GET requests are failing with SAM.