Identity management and privacy concerns are important to us. Our gateway services are accessed over the internet, and access is controlled through security applied with authentication and authorisation mechanisms to keep our systems and customer information safe.
Our services are restricted
Digital service providers wanting to integrate with us need to go through an approval process.
If you have any questions about identity and access or using gateway services, email [email protected]
Identity and access services
We provide 3 types of identity and access services to use with gateway services:
- OAuth authentication
- Machine-to-Machine authentication (M2M)
- SH authentication.
Identity and access software developer kit (SDK)
This authentication service is a token auth implementation using OAuth 2.0 for both cloud and native (desktop) client applications.
Machine-to-Machine (M2M) authentication
This authentication service utilises a client signed JSON Web Token (JWT) and is only available for service providers integrating through cloud service.
The service is available to use from April 2020 (R4 Release) for certain API services only.
This authentication service is only available for service providers integrating to secure FTP file transfer services.
How identity and access works
We provide mechanisms for authentication and authorisation for both the end user and organisation entity types. Our security protocols include transport layer encryption, digital certificates, and access tokens.
The end user authentication and authorisation mechanism is token authorisation (OAuth 2.0). Both cloud or native (desktop) application options are enforced for client applications and authenticate end users using their myIR user ID and password to grant the application access to their Inland Revenue information.
The organisational authentication and authorisation mechanisms include:
- Machine 2 Machine (M2M)
- SSH Keys.
The M2M mechanism uses a client signed JSON Web Token (JWT) to sign messages, which lets us identify the service provider or a customer of a service provider.
Secure FTP file transfer services require a service provider to supply their public PGP key for file encryption. We supply our public SSH key in order to gain access to the service provider FTP server.
Find out more about security measures:
The following security protocols apply when using our gateway services:
|Transport layer encryption||TLS||1.2|
|Digital certificates for mutual authentication||X.509||RFC 5280 profile|
Transport level security
At a network level, access to our services is restricted to approved providers. This includes access to our test environments.
For integration through a cloud end point:
- A TLS mutual authentication using the TLS 1.2 specification is applied across all gateway services in PROD and QUAL environments. This is not applicable for desktop client applications.
- In the mock services environment, TLS mutual authentication is not used but IP address white listing is applied.
TLS connection requirements:
|Cloud providers||Desktop providers|
|Incoming connections are identified using client side X509 certificates.||Desktop providers must connect through one-way TLS.|
|The client side X509 certificates must be from a certificate of authority and cannot be self-signed.||No client side X509 certificates required.|
Supporting guides and documents
Learn about the architecture of our gateway services and how we authorise identity and access to our application types.
Learn how to manage myIR logins for authorised representatives of an organisation so that access tokens can be generated for gateway services.
Use the Getting started guide to find out how to access our sandbox (mock services) and test environments.