Search

Search Results

Showing 1 - 10 of 33 results for

  • RealMe request parameters

    In general, it can be expected that SAML v2.0 products and libraries conform with the mandatory requirements of the OASIS SAML v2.0 standard. The New Zealand Security Assertion and Messaging Standard (NZSAMS) was published in 2008, and although this is occasionally still referenced, it is not d ...

  • Identity risk and authentication strength

    The recommended approach for starting business process design is to undertake an identity related risk assessment. This is used to determine which evidence of identity (EOI) process, if any, is required for the customers of the agency online service.The Department of Internal Affairs has produced&nb ...

  • SAML signing and encryption

    POST binding certificatesThe following sections describe how certificates are used in the RealMe context for both login and assertion service, assuming that POST binding is being used.Service Provider (SP) authentication request
    The SAML V2.0 AuthnRequest must be signed using the private key of the ...

  • Certificate purchasing

    SAML POST binding requirementsCompatible Certificate AuthoritiesIn the production and ITE environments, RealMe will trust certificates that organisations purchase from their preferred Certificate Authority provider. Certificates do not need to be the more costly Extended Validation (EV) ty ...

  • RealMe SAML exception handling

    For most of the common problems encountered in the RealMe® services, the web application handles the alternative process flow – for example, forgotten password or password expiry. For exceptions that cannot be handled by a process within the RealMe service, the user is redirected back to the agen ...

  • Business process design

    It's important to understand the difference between the RealMe login service and the RealMe assertion service when determining the possible fit for your organisation.RealMe® login service provides a single login, letting citizens use one username and password to access ...

  • Metadata requirements

    The SAML XML metadata file provides the RealMe service IdP with the required configuration parameters to enable integration. These include:
    EntityID
    Endpoints (Attribute Consumer Service)
    Public X.509 cert
    In most cases, there will be no difference in the SAML metadata values for the RealMe login se ...

  • List of SAML V2.0 components

    SAML components may be available as part of an enterprise product suite, a complete product with configuration tools that may require some development effort, or as code libraries that require a higher level of programming effort.Deployment is described as ‘enterprise’ where the product is under ...

  • Technical Considerations

    An organisation's choice of SAML Service Provider component and the way in which RealMe services are implemented are likely to be influenced by the online service environment and longer term roadmap. Based on our experience of more than 100 online service integrations, addressing the following quest ...

  • RealMe and SAML

    You will need to implement SAML v2.0 for your online service. Secure Assertion Markup Language (SAML) is the international standard from the Organization for the Advancement of Structured Information Standards (OASIS) which ensures secure messaging between your online website and RealMe® servi ...