Skip to content.
|Networking government in New Zealand.
Archive

Archived articles:

See archives for this section
 

Table of Contents

This document contains the following sections:

O Foreword

Part 1 - Overview of NZ SAMS

Overview of Part 1
1 Introduction
2 Scope

3 Background

4. Application of Standard

5. Guiding Principles for NZ SAMS

6. Authentication: OASIS SAML v2.0 Profiles and Bindings for New Zealand Government Deployments.

6.1 Authentication: Profiles and Bindings introduction
6.2 Authentication: NZ government generic usage patterns mapped to SAML v2.0 Profiles

6.3 Authentication: OASIS SAML v2.0 SSO Bindings

6.4 Deploying selected SAML v2.0 SSO bindings - Compliance Overview

7. Summary of Compliance Requirements from Part 1

Part 2 - Constraints on OASIS SAML v2.0 for New Zealand Government Deployments as NZ SAMS

Appendices

Tables

Table 1 – Authentication standards and documents
Table 2 – Conformance and compliance requirements
Table 3 – Message flows for SSO binding set one
Table 4 – Message flows for SSO binding set two
Table 5 – Summary of Part 1 compliance requirements
Table 6 – NZ SAMS constraints on OASIS SAML v2.0 conformance requirements
Table 7 – NZ SAMS constraints on OASIS SAML v2.0 metadata
Table 8 – NZ SAMS constraints on the OASIS SAML v2.0 Web Browser SSO Profile
Table 9 – NZ SAMS constraints on the OASIS SAML v2.0 bindings
Table 10 – NZ SAMS constraints on the OASIS SAML v2.0 core (Assertions and Protocols)
Table 11 – NZ SAMS constraints on OASIS SAML v2.0 authentication context
Table B1 – SAML v2.0 specifications and profiles for constraint into NZ SAMS for Release 1.0 – authentication
Table B2 - SAML v2.0 specifications and profiles for constraint into NZ SAMS for subsequent releases

Figures

Figure 1 – Outline of interactions with all-of-government authentication services
Figure 2 – Generic NZ government usage pattern
Figure 3 – SP initiated Web SSO profile
Figure 4 – IdP Proxy (IdP Extended)
Figure 5 – SP initiated with Name Identifier Mapping profile
Figure 6 – SSO binding set 1 – HTTP Redirect and HTTP Post
Figure 7 – SAML v2.0 SSO binding set 2 – HTTP Redirect and HTTP Artifact with the Artifact Resolution profile
Figure A1 – ESAA use case
Figure A2 – Interaction Model for ESAA usage of SAML v2.0
Figure A3 – Assert Identity (Functional Model)
Figure A4 – Generic example of a user obtaining an assertion of identity (Interaction Model)
Figure A5 – MAF SSO scenario 2 – shared transactions (Functional Model)
Figure A6 – Overview of messaging (Functional Model)
Figure A7 – Interaction Model for GLS SAML v1.1 implementation


[ Previous | Next ]