Use shared_ptr in Restriction sets instead of unique_ptr

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.10
    • Affects Version/s: None
    • Component/s: None
    • None
    • Minor Change
    • Platforms 2017-07-10
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The way we actually want to use Restriction sets in the RolesGraph and on User objects means that we potentially want to create many common references to the same authenticationRestrictions and their cross-products.

      This means either making them sharable, or at the very least copyable. Let's go for shared_ptrs and simplify our lives.

            Assignee:
            Sara Golemon (Inactive)
            Reporter:
            Sara Golemon (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: