1 / 12

SPML Core Identity Schema

SPML Core Identity Schema. A discussion document. Agenda. What is the core identity schema? Source materials Proposed schema. What is the core identity schema?. Basic identity schema around which SPML operations are built Core point for identity attributes

oki
Download Presentation

SPML Core Identity Schema

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SPML Core Identity Schema A discussion document

  2. Agenda • What is the core identity schema? • Source materials • Proposed schema

  3. What is the core identity schema? • Basic identity schema around which SPML operations are built • Core point for identity attributes • Mapping point for core attributes • Start point for extensions

  4. Source materials • Existing efforts that include an identity schema are: • OASIS CIQ • DMTF CIM • X.500/LDAP standard schema • More to consider?? • Step through them:

  5. CIQ • OASIS XML standard for name and address data management eXtensible Name and Address Language (xNAL) • Two components • xNL : eXtensible Name Language to describe name components • xAL : eXtensible Address Language to describe address components • xCIL: Extensible Customer Information Language describes additional “customer” related data (vehicles, contact times) • xCRL: Extensible Customer Relationships Language for representing relationships (org-org, person to group)

  6. CIQ - Names Mr.Ram V. Kumar C/O Privacy Link PO Box: 773, Chatswood, NSW 2057, Australia <xNAL> <Record> <xNL> <NameDetails PartyType="Person"> <NameLine>Ram V Kumar</NameLine> <DependencyName PartyType="Organisation" DependencyType="C/O"> <NameLine>PrivacyLink</NameLine> </DependencyName> </NameDetails> </xNL> <xAL> <AddressDetails> <Address>POBox: 773, Chatswood,NSW 2057, Australia</Address> </AddressDetails> </xAL> </Record> </xNAL>

  7. CIQ - Addresses 23 Archer Street Chatswood, NSW 2067 Australia <xAL> <AddressDetails AddressType="Residential"> <Country> <CountryName>Australia</CountryName> <Locality> <LocalityName>NSW</LocalityName> <DependentLocality> <DependentLocalityName>Chatswood</DependentLocalityName> <Thoroughfare> <ThoroughfareName>23 Archer Street</ThoroughfareName> </Thoroughfare> </DependentLocality> <PostalCode> <PostalCodeNumber>2067</PostalCodeNumber> </PostalCode> </Locality> </Country> </AddressDetails> </xAL>

  8. CIQ –Data • <xCIL> • <CustomerDetails> • <CustomerID>SS123321</CustomerID> • <NameDetails PartyType="Person"> • <NameLine>Miss. Nivetha Sakthi</NameLine> • </NameDetails> • <PersonInfo> • <ContactNumbers> • <ContactNumber Type="Telephone"> • <Number>243-448-5152</Number> • </ContactNumber> • <ContactNumber Type="Fax"> • <Number>248-448-5150</Number> • </ContactNumber> • </ContactNumbers> • <EmailAddresses> • <EmailAddress Type="Business">nivetha@sakthisoft.com </EmailAddress> • </EmailAddresses> • <Occupations> • <Occupation> • <FreeTextLine Type="Position"> Software Engineer(Full-Time) </FreeTextLine> • <FreeTextLine Type="Department">Products Division</FreeTextLine> • <FreeTextLine Type="Organisation Name"> SakthiSoft, Inc </FreeTextLine> • <OrganisationAddress> • <AddressDetails> • <Address> Floor 4, Ste 5, Block C Carnegie VIII 43 West Archer Street Boulder, CO 80302-4598, USA </Address> • </AddressDetails> • </OrganisationAddress> • <ManagerName> • <FreeTextLine>Ms. Shantha Devi</FreeTextLine> • </ManagerName> • </Occupation> • </Occupations> • </PersonInfo> • </CustomerDetails> • </xCIL>

  9. CIQ – Relationships • <xCRL> • <RelationshipRecord> • <Customer PartyType="Person"> • <NameDetails> • <NameLine>Mrs.MaryJohnson</NameLine> • </NameDetails> • <PersonInfo> • <FreeTextLine Type="Email">mjohnson@sakthisoft.com</FreeTextLine> • </PersonInfo> • </Customer> • <InRelationshipWith RelationshipType="Person-Person"> • <Customer PartyType="Person"> • <NameDetails> • <NameLine>Mr.Patrick Johnson</NameLine> • </NameDetails> • <PersonInfo> • <FreeTextLine Type="Email"> pjohnson@sakthisoft.com </FreeTextLine> • </PersonInfo> • </Customer> • <RelationshipInformation> • <PrimaryCustomerRelationshipTitle> WIFE </PrimaryCustomerRelationshipTitle> • <SecondaryCustomerRelationshipTitle> HUSBAND </SecondaryCustomerRelationshipTitle> • <CommonEntities> • <AddressDetails> • <Address> Floor 4, Ste 5, Block C Carnegie VIII 43 West Archer Street Boulder, CO 80302-4598, USA </Address> • </AddressDetails> • <PersonInfo> • <FreeTextLine Type="Telephone Number">243-448-5152</FreeTextLine> • <FreeTextLine Type="Fax Number">243-448-5150</FreeTextLine> • </PersonInfo> • </CommonEntities> • </RelationshipInformation> • </InRelationshipWith> • </RelationshipRecord> • </xCRL>

  10. CIM • Common Information Model (DMTF) • Taken from user security schema • Candidates: • Person • Org • OrgUnit

  11. CIM • Person • Name: • BusinessCategory: • CommonName: • EmployeeNumber: • EmployeeType: • FacsimileTelephoneNumber: • HomePhone: • HomePostalAddress: • JpegPhoto: • LocalityName: • Manager: • Mobile: • OU: • Pager: • PostalAddress: • PostalCode: • PreferredLanguage: • Secretary: • StateOrProvince: • Surname: • TelephoneNumber: • Title: • Organization • CreationClassName: • Name: string • BusinessCategory: • FacsimileTelephoneNumber: • LocalityName: • Mail: • OrganizationName: • PostalAddress: • PostalCode: • StateOrProvince: • TelephoneNumber: • OrgUnit • CreationClassName: • Name: • BusinessCategory: • FacsimileTelephoneNumber: • LocalityName: • OU: • PostalAddress: • PostalCode: • StateOrProvince: • TelephoneNumber:

  12. LDAP/RFC • Take from basic top-down as required: • RFC 2256 User Schema

More Related