Uploaded image for project: 'Sentry (Retired)'
  1. Sentry (Retired)
  2. SENTRY-478

Solr Sentry plug-in integration with DB store

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Implemented
    • Affects Version/s: None
    • Fix Version/s: 1.5.0
    • Component/s: None
    • Labels:
      None

      Description

      Currently Solr does support index-level security via sentry with file as backend privilege store. Using file as the backend store is simple, but there has some disadvantages as followings:
      1. Can't satisfied with the needs of dynamically add, delete and update permissions
      2. Can't be centrally managed and difficult to maintain
      According to the above disadvantages, The Solr Sentry plug-in integration with DB store is demanded. The Hive Sentry plug-in has already integration with DB store, but the Hive authorization model is different from the Solr authorization model.So this new feature depends on the generic authorization model(SENTRY-398).

        Attachments

        1. SENTRY-478.003.patch
          85 kB
          shenguoquan
        2. SENTRY-478.004.patch
          85 kB
          shenguoquan
        3. SENTRY-478.005.patch
          98 kB
          shenguoquan
        4. SENTRY-478.006.patch
          100 kB
          shenguoquan
        5. SENTRY-478.007.patch
          93 kB
          shenguoquan
        6. SENTRY-478.008.patch
          87 kB
          shenguoquan
        7. SENTRY-478.009.patch
          88 kB
          shenguoquan
        8. SENTRY-478.010.patch
          67 kB
          shenguoquan
        9. SENTRY-478.011.patch
          70 kB
          shenguoquan
        10. SENTRY-478.012.patch
          70 kB
          shenguoquan

          Issue Links

            Activity

              People

              • Assignee:
                guoquan shenguoquan
                Reporter:
                guoquan shenguoquan

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Issue deployment