Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.3.0.0-incubating
    • Security
    • None

    Description

      RPS service address exposing to end-user is not secure, and we should not expose it out.

      *Case 1: When master RPS is down, changing to standby RPS*
      Current behavior
      ```
      postgres=# select * from a;
      WARNING: ranger plugin service from http://test1:8432/rps is unavailable : Couldn't connect to server, try another http://test5:8432/rps
      ERROR: permission denied for relation(s): public.a
      ```
      Warning should be removed.
      Expected
      ```
      postgres=# select * from a;
      ERROR: permission denied for relation(s): public.a
      ```

      *Case 2: When both RPS are down, should only print that RPS is unavailable.*
      Current Behavior:
      ```
      postgres=# select * from a;
      WARNING: ranger plugin service from http://test5:8432/rps is unavailable : Couldn't connect to server, try another http://test1:8432/rps
      ERROR: ranger plugin service from http://test1:8432/rps is unavailable : Couldn't connect to server. (rangerrest.c:463)
      ```
      Expected
      ```
      postgres=# select * from a;
      ERROR: ranger plugin service is unavailable : Couldn't connect to server. (rangerrest.c:463)
      ```

      The warning message should be printed in cvs log file.

      Attachments

        Issue Links

          Activity

            People

              wlin Wen Lin
              wlin Wen Lin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Slack

                  Issue deployment