-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
11 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,29 +1,29 @@ | ||
| === tierDocThoughts.adoc | ||
|
|
||
| ==== Comprehensive Guide to Internet2’s Identity and Access Management Portfolio | ||
| === Comprehensive Guide to Internet2’s Identity and Access Management Portfolio | ||
| - - - | ||
| ===== Introduction | ||
| ==== Introduction | ||
| - - - | ||
| ===== Part 1: The Identity Aspects of Identity and Access Management | ||
| ==== Part 1: The Identity Aspects of Identity and Access Management | ||
|
|
||
| ======= 1.1 Systems of Record Provide Facets of a Person’s Digital Identity (9) | ||
| ====== 1.1 Systems of Record Provide Facets of a Person’s Digital Identity (9) | ||
|
|
||
| ======= 1.2 How to Represent Digital Identities: Schemas and Schema Mapping (5) | ||
| ====== 1.2 How to Represent Digital Identities: Schemas and Schema Mapping (5) | ||
|
|
||
| ======= 1.3 ID Matching: Approaching the Ideal of One Digital Identity per Person (6) | ||
| ====== 1.3 ID Matching: Approaching the Ideal of One Digital Identity per Person (6) | ||
|
|
||
| - - - | ||
| ===== Part 2: Specifying Who Should Have Access to What Services and Resources (3) | ||
| ==== Part 2: Specifying Who Should Have Access to What Services and Resources (3) | ||
|
|
||
| ======= 2.1 Enriching Identity: Building Group Memberships That Express a Person’s Relationships to Institutional Structures and Processes (2) | ||
| ====== 2.1 Enriching Identity: Building Group Memberships That Express a Person’s Relationships to Institutional Structures and Processes (2) | ||
|
|
||
| - - - | ||
| ===== Part 3: Provisioning and De-provisioning: Making Reality Match What Should Be the Case (8) | ||
| ==== Part 3: Provisioning and De-provisioning: Making Reality Match What Should Be the Case (8) | ||
|
|
||
| - - - | ||
| ===== Part 4: Integration Strategies: Leveraging APIs and Event-Driven Messaging to Tie IAM into the Overall IT Environment (1,7, 14) | ||
| ==== Part 4: Integration Strategies: Leveraging APIs and Event-Driven Messaging to Tie IAM into the Overall IT Environment (1,7, 14) | ||
|
|
||
| - - - | ||
| ===== Part 5: API AuthNZ, Non-Person Entities and Their Management (4, 13) | ||
| ==== Part 5: API AuthNZ, Non-Person Entities and Their Management (4, 13) | ||
|
|
||
| - - - |