...
Help education and research organizations solve the Identity and Access Management (IAM) challenges they encounter
By providing open source implementations of key IAM capabilities and assuring their long-term sustainability
By standardizing
How applications (whether local, federated or SaaS) integrate with IAM infrastructure
How existing institutional IAM infrastructure can interoperate with TIER components to provide a full IAM service suite
TIER Entity Registry and Data Structures and APIs Working Groups
The TIER Entity Registry Working Group and the TIER Data Structures and APIs Working Group share the following key goals
DevelopTo define integration and interoperability strategies and models
To help charter development projects that address specific gaps in existing open source IAM packages
TIER Entity Registry WG and Data Structures and APIs WG Tasks
To develop a comprehensive functional model of IAM
To define and adopt specifications for the resource schema and interfaces needed to deliver identity and access management (IAM) services
- Between the various TIER IAM components
- Between TIER components and the rest of the institutional IT landscape, both on premise and in the cloud
- Provide guidance on building IAM infrastructure and processes that accord with the TIER model
Standards, Tools and Guidelines set out in TIER Release1
...
- The canonical specification language for HTTP-oriented APIs in TIER is Swagger 2.0
- Why Swagger and not RAML? After all, RAML is pretty cool or API Blueprint?
- In the move from version 1 to version 2, Swagger incorporated a lot of
- RAML
- 's best features (around reusable definitions, etc.)
- Swagger 2 has been adopted as the basis for further development by the industry-launched Open API Initiative (http://openapis.org) and that should strengthen the already thriving Swagger developer and adopter community
Key Deliverables for TIER R1
...