can choose a provider and use their existing identity. Identity assurance and 2 Partner An NGO partner accessing agency trust when accepting Agency information stored in an agency ICT partner identities system or API The partner may have a In the Store’ model above, the ‘App large user base which individual partner accessing cannot effectively be information stored in an agency ICT provisioned prior to their system or API first service access 3 Partner attempt. Same as the above, with the ICT system being whole-of-government Providing choice of 4 Customer Customers accessing agency credentials to customers Agency services Strong customer Businesses accessing agency identification services Remote and In-person Volunteers accessing agency identity proofing systems Security and customer 5 Customer privacy control including As above, however the agency has pseudonymous access Partner also outsourced the ICT provision Existing know-customer 6 Customer Customers accessing online services scenarios and agency provided e.g. One Stop-Shop identity provider MyAccount and Payments Portals Consumer identity 7 Government-as-an-Identity Provider standards support to support API access for: Consumer platform support Customer Developers’ building ‘Citizen Developer portal mobile apps and orchestrations registration across government services API Key authentication Partners developing customer Delegated access to applications agency API’s Registered access to Open Data sets to increase online/query capabilities Sharing a single application 8 Agency Agency staff accessing a shared instance typically requires whole-of-government service e.g. the a single identity source Gov2Gov intranet or the Leveraging existing agency Room Booking system identities to avoid 9 As however the ICT provision Leveraging existing agency has also been outsourced Partner credentials to Providing a Single Sign-on (SSO) experience as if
can choose a provider and use their existing identity. 2 Partner Agency An NGO partner accessing agency information stored in an agency ICT system or API In the ‘App Store’ model above, the individual partner accessing information stored in an agency ICT system or API Identity assurance and trust when accepting partner identities The partner may have a large user base which cannot effectively be provisioned prior to their first service access attempt. 3 Partner Same as the above, with the ICT system being whole-of-government 4 Customer Agency Customers accessing agency services Businesses accessing agency services Volunteers accessing agency systems Providing choice of credentials to customers Strong customer identification Remote and In-person identity proofing Security and customer privacy control including pseudonymous access Existing know-customer scenarios and agency identity provider 5 Customer Partner As above, however the agency has also outsourced the ICT provision 6 Customer Customers accessing online services provided e.g. One Stop-Shop MyAccount and Payments Portals 7 Customer Government-as-an-Identity Provider to support API access for: ‘Citizen Developers’ building mobile apps and orchestrations across government services Partners developing customer applications Registered access to Open Data sets to increase online/query capabilities Consumer identity standards support Consumer platform support Developer portal registration API Key authentication Delegated access to agency API’s 8 Agency Agency staff accessing a shared whole-of-government service e.g. the Gov2Gov intranet or the Room Booking system Sharing a single application instance typically requires a single identity source Leveraging existing agency identities to avoid Leveraging existing agency credentials to Providing a Single Sign-on (SSO) experience as if 9 Partner As however the ICT provision has also been outsourced