Versions Compared

Old Version 10

changes.mady.by.user Jeff Ruch (colostate.edu)

Saved on

compared with

New Version Current

changes.mady.by.user Jeff Ruch (colostate.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

    1. Types of groups

      1. Describe how your product supports a list of definable groups.

      2. Describe how your product supports a hierarchy of groups (i.e., nesting and relationships between groups)

        1. What entities can be members of groups?

      3. ?? What upstream data sources does your product readily support?

      4. Do you support sets of groups associated together? (i.e., base, exceptions, includes/excludes)

    2. Administration

      1. Describe delegated access administration features for group management.

      2. How does your product deal with “orphaned” delegation? (When previous admins are no longer there.)

      3. Do you provide APIs that would allow an external group and access management tool to drive your product’s groups and group memberships

      4. Do you support attribute-based (ABAC) or role-based (RBAC) concepts to drive groups and group membership?

      5. Can groups have permissions associated with them?

      6. What sort of attributes or metadata about groups are available?

      7. Does your product support automatic review of roles/groups (attestation)?

    3. Guidance for architecting

      1. How does your product expose or link groups or roles for fine-grained service authorizations?

      2. How do you support Attribute-based access control?

      3. How do you support Role-based access control?

        1. Are roles managed within the product?

      4. How does your product define a default role or template (set of groups) for new entities?

      5. How are groups updated/kept in sync?

      6. Describe synchronization mechanisms, i.e., changelog vs. full sync

10. Product Cost/Venor Vendor Considerations

    1. LicenceLicense

      1. What is your Software licensing cost structure  (Enterprise vs non)? The software is open source.  I don't believe there are separate versions.  Enhancements are submitted through JIRA.  Enhancements requests are driven by customers with support contracts.
      2. If one of your license model is pay-per-active-account , how do you consider  the following populations? : N/A
        1. Alumni users 
        2. Guest users
        3. Extended Community users (Parents, Propsect Students , Applicants, Continuing Ed students ,ec..)
        4. Social identities that are linked to Idm system
      3. Do you provide  any Higher Ed discount ? N/A
    2. Vendor Support and Maintenance  (On going)
      1. What is your on-going service support  contract structure ?  There are two support subscription models (8x5, and 24x7).
    3. Vendor Stability 
      1. How long is your product being in the market ? The source code originated in 2011.  There are 34 contributors, 49 releases and 18,500 commits.  The project is active and there are daily commits.
      2. How many Higher Ed clients do you have ? Three listed in their references (University of Illinois, Western University Canada, University of Selye).