Sign in

Introduction

Access Exchange is an orchestrator and security broker for integration with Internet of Things-enabled devices, created to make session management simple, safe and intuitive. This document serves as a first look and basic introduction to Access Exchange, as well as a summary of how to set up and manage your own IoT client project.

Before you start

This section describes basic steps new or potential new clients should take to initiate a project aiming at implementing and integrating Division X’s Access Exchange into their own products.

Client roles

Implementing Access Exchange may require a close collaboration between the new client organisation and the Access Exchange team. Experience from prior implementations tells us it is vital that the client has a clear understanding of their responsibilities early in the process.
We ask that all clients define and incorporate these roles in their integration project:

  • Project manager – Overarching responsibility for progress, reporting and decision-making.

  • Technical architect – Technical lead at client.

  • Operation & support manager – Responsible for operations.

    Please note that the above roles outline areas of responsibility, and are not necessarily separate people with separate resources. Additionally, it is important to incorporate these fields of responsibilities as early as possible:

  • Responsibility for user data mapping of existing processes and business objects (quality assurance)

  • Responsibility for the migration process of privacy related datasets

  • Responsibility for privacy configuration and privacy request lifecycle

Standardised integration process

We have defined a standardised integration process that each new integration should adhere to. This process can be adapted by the client project with respect to its scope and complexity.

alt text

  1. Analyze the needs and shape of your client project.
  2. Define the exact scope of integration
  3. High level integration architecture
  4. Mapping of integration touchpoints between Access Exchange and client’s existing applications
  5. Establishing connection between applications and orchestrator
  6. Testing/acceptance test of connection to orchestrator
  7. Prepare for production rollout
  8. Production deployment
  9. Monitoring and quality assurance
  10. Monitoring and management of errors via orchestrator.
  11. Maintenance and reporting
  12. Retrospective analysis with improvements and suggestions

INTEGRATION DETAILS

Environments

These are the URLs to use:

Environment URL
Sandbox https://sandbox.api.telia.io
Production https://api.telia.io

Setup and structure

Client setup begins with an entry on Access Exchange’s self-provisioning, self-managing platform. An account is created there and an email with the relevant details is sent, which begins your journey onto the platform. Please take some time to get acquainted with its various parts and functions. The “Get going” page is good place to start.

When you feel comfortable navigating around the platform, you may wish to head over to the documentation. Under “Open API”, you will find resources for generating your code. Access tokens for web API:s are also found on this platform, under the “API” menu. Here you can create a user-specific key, which is then used along with your User ID to log onto the desired API.

On the platform, device providers will find instructions for taking ownership of devices. As an owner, device provider or service provider, you will also find resources for creating certificates, as well as information on the relevant protocols (CDO XMPP and CDO Admin XMPP) used by Access Exchange.

alt text