Verified identity data

The elements provided to organisations requesting verified identity can include full name, gender, date of birth and place of birth along with the federated identity tag. DIA's Identity Verification Service should only provide the data required for the agency's business process, and the specific elements are configured as part of the integration. Following recent legislation changes, the RealMe identity photo is now available in some circumstances.

Identity data is provided as JSON or XML, and the online service needs to cater for the formats described in the table below. During integration, the RealMe team can provide test cases that include data limit testing examples.

XML format

Verified identity data table

 

JSON format

Verified identity data table Json format

An example identity in XML is illustrated below.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns4:Party xmlns:ns1="urn:oasis:names:tc:ciq:xnl:3" xmlns:ns2="urn:oasis:names:tc:ciq:ct:3" xmlns:ns3="http://www.w3.org/1999/xlink" xmlns:ns4="urn:oasis:names:tc:ciq:xpil:3" xmlns:ns5="urn:oasis:names:tc:ciq:xal:3" xmlns:ns6="urn:nzl:govt:ict:stds:authn:deployment:GLS:ContactDetails:v1"><ns4:PartyName>
<ns1:PersonName ns2:DataQualityType="Valid"><ns1:NameElement ns1:ElementType="FirstName">Roberta</ns1:NameElement><ns1:NameElement ns1:ElementType="MiddleName">Janice</ns1:NameElement><ns1:NameElement ns1:ElementType="LastName">Whitlam</ns1:NameElement></ns1:PersonName>
</ns4:PartyName><ns4:PersonInfo ns4:Gender="F"/>
<ns4:BirthInfo ns2:DataQualityType="Valid"><ns4:BirthInfoElement ns4:Type="BirthYear">1983</ns4:BirthInfoElement><ns4:BirthInfoElement ns4:Type="BirthMonth">03</ns4:BirthInfoElement><ns4:BirthInfoElement ns4:Type="BirthDay">13</ns4:BirthInfoElement><ns4:BirthPlaceDetails ns2:DataQualityType="Valid"><ns5:Country><ns5:NameElement ns5:NameType="Name">New Zealand</ns5:NameElement></ns5:Country><ns5:Locality><ns5:NameElement ns5:NameType="Name">Welington</ns5:NameElement></ns5:Locality></ns4:BirthPlaceDetails></ns4:BirthInfo></ns4:Party>

 

An example identity in JSON is illustrated below.

{"transactionId":"_823B8A5F8B55B38DC529EB2CE5907ECE","name":{"firstName":"Agency","middleName":"Data","lastName":"One"," ":false},
"placeOfBirth":{"locality":"AUCKLAND","country":"New Zealand","placeOfBirthDisputed":false},
"gender":{"genderValue":"M","genderDisputed":false},"dateOfBirth":{"dateOfBirthValue":"1981-11-11","dateOfBirthDisputed":false}}

 

The 35 character Federated Identity Tag (FIT) - which is unique for each combination of person and online service (privacy domain), is also contained in the assertion response. An example is shown below.

<saml2:NameID xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion" 
Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
NameQualifier="https://identity.qa.i.govt.nz/ivs/idp">WQAB94CD15736B863ADE05318581CAC9868</saml2:NameID>