5. SCIM(System for Cross-domain Identity
Management)
• 目的(http://tools.ietf.org/html/draft-ietf-scim-core-schema-00より)
• The System for Cross-Domain Identity Management (SCIM) specification is designed
to make managing user identity in cloud based applications and services easier. The
specification suite builds upon experience with existing schemas and deployments,
placing specific emphasis on simplicity of development and integration, while
applying existing authentication, authorization, and privacy models. Its intent is to
reduce the cost and complexity of user management operations by providing a
common user schema and extension model, as well as binding documents to
provide patterns for exchanging this schema using standard protocols. In essence,
make it fast, cheap, and easy to move identity in to, out of, and around the cloud.
This document provides a platform neutral schema and extension model for
representing users and groups in JSON and XML formats. This schema is intended for
exchange and use with cloud service providers. Additional binding documents
provide a standard REST API, SAML binding, and use cases.
7. Graph API
• 目的(https://developers.facebook.com/blog/post/377/より)
• Any webpage can now easily become part of the social graph
• On Facebook, users build their profiles through connections to what they care about
— be it their friends or their favorite sports teams, bottles of wine, or celebrities.
The Open Graph protocol opens up the social graph and lets your pages become
objects that users can add to their profiles. When a user establishes this connection
by clicking Like on one of your Open Graph-enabled pages, you gain the lasting
capabilities of Facebook Pages: a link from the user's profile, ability to publish to the
user's News Feed, inclusion in search on Facebook, and analytics through our
revamped Insights product.
• In summary, by giving your users better, simpler ways to connect with the content
on your site, you can then use those connections to provide more personalized,
relevant experiences. And the product only gets better over time. The more people
that come back to your site, the more connections that are made, the better your
service becomes.
8. Graph API
• ソーシャル Graph を管理するための API
• オブジェクトの表現方法
• JSON
• Schema や Object / Connection の種類はサービス毎に定義
• オブジェクトの管理方法
• RESTful
• サービス毎に定義
• 採用製品/サービス
• Facebook / Graph API
• Microsoft / Windows Azure Active Directory Graph API
10. 参考)WAAD が Graph API を採用した理
由
• Kim Cameron の blog(http://www.identityblog.com/?p=1222)
• It is because of the central importance of graph technology in being able to manage
connectedness - something that is at the core of the digital universe. Treating the
world as a graph allows us to have a unified approach to querying and
manipulating interconnected objects of many different kinds that exist in many
different relationships to each other.
• A directory has emerged that by August is projected to contain one billion users.
True, it's only one directory in a world with many directories (most agree too many).
But beyond the importance it achieves through its scale, it fundamentally changes
what it means to be a directory: it is a directory that surfaces a multi-dimensional
network.
• This network isn't simply a network of devices or people. It's a network of people
and the actions they perform, the things they use and create, the things that are
important to them and the places they go. It's a network of relationships between
many meaningful things. And the challenge is now for all directories, in all
domains, to meet a new bar it has set.
18. 参考)オブジェクト間のつながりの表現
• Graph の目指すもの・利点
• Multi dimensional protocol の必要性
• クラウドでは人、アプリケーションなどのオブジェクトが中央のディ
レクトリを通じて連携しない
• 関係性を柔軟に表現できる必要がある
• 方向付けの表現(雇用と所属など)
Apps person
person use Apps
use work
belong directory Services
organizat
organizat ion contract
ion Services