Reset Search
 

 

Article

OAuth API Query - Version 2.0

« Go Back

Information

 
Article No:000013469
Question
Twinfield is moving to OAuth 2.0 Security

This article is divided into two sections

1.)  You do not yet use OAuth and want to start using it. You already use OAuth 1.0 and want to know how to migrate. 
2.) 
OAuth 2.0 has already been implemented but is not yet registered with Twinfield or  OAuth 2.0 has already been implemented and is already registered with Twinfield.
 
Answer
Data security is of the utmost importance to Wolters Kluwer. When working with us as an Accountant, Reseller, Business or Integration partner, you rely on us to handle your data securely. We know that the many connections between different software applications and Twinfield Accounting must be – and remain – secure and efficient. Therefore, we are switching to a new and more secure connection method. 
With that in mind we are now informing all our connected parties that if they are integrating with Twinfield,  they must implement OAuth 2.0 by 30 April 2021.
The benefits of OAuth 2.0 are:
  • OAuth 2.0 is the standard authentication and authorisation protocol. It protects user data by granting access to data without revealing the identity or login details of the user. 
  • It uses tokens to grant limited access to the user's data. Instead of using cookies, sessions or other technologies, a temporary access token is used to obtain access to a particular data range.
  • It is no longer necessary to have our clients pass on a username and password to establish a connection. 
  • It requires the consent of the user.
What does this mean for Accountants and Businesses using Twinfield?
Twinfield software partners may have to contact all users to ask them to re-authenticate their connections. As the authentication of connections occurred only once before, it may be that not all users are aware of their login details. 
Do you have connections with Twinfield? Then follow the steps below.
Migrating to OAuth 2.0 
This section is intended for the following target group: 
  • You do not yet use OAuth and want to start using it. 
  • You already use OAuth 1.0 and want to know how to migrate. 
Next steps  
Go to the Developers Portal. You can find information or create a new Wolters Kluwer Account here. This is a secure way of logging in thanks to the use of multifactor authentication, which is exclusively used to obtain access to the Developers Portal. Click here for more information about the Wolters Kluwer Account. 
Once you have logged in to the Wolters Kluwer Account, you can register with your client-ID. You can manage your OAuth credentials yourself using this registration. 

Migration to OAuth 2.0 already completed 
This section is intended for the following target group: 
  • OAuth 2.0 has already been implemented but is not yet registered with Twinfield. 
  • OAuth 2.0 has already been implemented and is already registered with Twinfield. 
Implementation completed?
Now inform your client and ask him/her to re-authenticate the connection.  
If you would prefer to speak to a technical consultant, please use this form.  
If the above information is not relevant for you, we kindly ask you to forward this e-mail to the colleague (e.g., IT manager) responsible for the connection to Twinfield Accounting. 
Could you please make sure that these modifications are made on time to ensure that you are not prevented from logging in with outdated protocols from 1 May 2021 By starting implementation early, we can provide any required support if you have any questions or problems.   
Together we can ensure that the connections with our software partners can be used securely.
Support for software integration partners.
We have included an article which explains various concepts related to partner connections, including connection user, API, web service, web service authentication, Open ID Connect (OIDC), OAuth2 and Single Sign-On (SSO) in our Knowledge Base. If you would prefer to speak to a technical consultant after reading all the available information, please use this form. If you have any questions, please see our Partner Support community
Future of the Developers Portal
As well as offering a personal portal where it is easy to securely manage OAuth login details yourself and where you can view all information about connections in one place, we are working hard on the following features, which will be available in the portal in the coming year: 
  • Multiple developers in a single portal using a personal Wolters Kluwer Account.
  • Requesting certification from within the Developers Portal.
  • Requesting access to the demo environment from within the Developers Portal.
  • Publishing WebAPIs for the NEO functionalities. 
  • The web page www.twinfield.nl/api will be moved to the Developers Portal, so that everything can be found in one place. 

This section of the article is meant for the following target group. 

Migrating to OAuth 2.0 
  • You do not yet use OAuth and want to start using it. 
  • You already use OAuth 1.0 and want to know how to migrate. 


Data security is of the utmost importance to Wolters Kluwer. When working with us as an Accountant, Reseller, Business or Integration partner, you rely on us to handle your data securely. We know that the many connections between different software applications and Twinfield Accounting must be – and remain – secure and efficient. Therefore, we are switching to a new and more secure connection method. 
With that in mind we are now informing all our connected parties that if they are integrating with Twinfield,  they must implement OAuth 2.0 by 30 April 2021.
The benefits of OAuth 2.0 are:
  • OAuth 2.0 is the standard authentication and authorisation protocol. It protects user data by granting access to data without revealing the identity or login details of the user. 
  • It uses tokens to grant limited access to the user's data. Instead of using cookies, sessions or other technologies, a temporary access token is used to obtain access to a particular data range.
  • It is no longer necessary to have our clients pass on a username and password to establish a connection. 
  • It requires the consent of the user.
What does this mean for Accountants and Businesses using Twinfield?
Twinfield software partners may have to contact all users to ask them to re-authenticate their connections. As the authentication of connections occurred only once before, it may be that not all users are aware of their login details. 
Do you have connections with Twinfield? Then follow the steps below

 Next steps  
Go to the Developers Portal. You can find information or create a new Wolters Kluwer Account here. This is a secure way of logging in thanks to the use of multifactor authentication, which is exclusively used to obtain access to the Developers Portal. Click here for more information about the Wolters Kluwer Account. 
Once you have logged in to the Wolters Kluwer Account, you can register with your client-ID. You can manage your OAuth credentials yourself using this registration. 
Implementation completed?
Now inform your client and ask him/her to re-authenticate the connection.   
Migration to OAuth 2.0 already completed 
This section is intended for the following target group: 
  • OAuth 2.0 has already been implemented but is not yet registered with Twinfield. 
  • OAuth 2.0 has already been implemented and is already registered with Twinfield. 
Next steps  
Go to the Developers Portal. You can find information or create a new Wolters Kluwer Account here. This is a secure way of logging in thanks to the use of multifactor authentication, which is exclusively used to obtain access to the Developers Portal. Click here for more information about the Wolters Kluwer Account. 
Once you have logged in to your Wolters Kluwer Account, you can register with your client ID. You can manage your OAuth credentials yourself using this registration. 
Implementation completed?
Now inform your client and ask him/her to re-authenticate the connection.  
If you would prefer to speak to a technical consultant, please use this form.  
If the above information is not relevant for you, we kindly ask you to forward this e-mail to the colleague (e.g., IT manager) responsible for the connection to Twinfield Accounting. 
Could you please make sure that these modifications are made on time to ensure that you are not prevented from logging in with outdated protocols from 1 May 2021? By starting implementation early, we can provide any required support if you have any questions or problems.   
Together we can ensure that the connections with our software partners can be used securely.
Support for software integration partners.
We have included an article which explains various concepts related to partner connections, including connection user, API, web service, web service authentication, Open ID Connect (OIDC), OAuth2 and Single Sign-On (SSO) in our Knowledge Base. If you would prefer to speak to a technical consultant after reading all the available information, please use this form. If you have any questions, please see our Partner Support community
Future of the Developers Portal
As well as offering a personal portal where it is easy to securely manage OAuth login details yourself and where you can view all information about connections in one place, we are working hard on the following features, which will be available in the portal in the coming year: 
  • Multiple developers in a single portal using a personal Wolters Kluwer Account.
  • Requesting certification from within the Developers Portal.
  • Requesting access to the demo environment from within the Developers Portal.
  • Publishing WebAPIs for the NEO functionalities. 
  • The web page www.twinfield.nl/api will be moved to the Developers Portal, so that everything can be found in one place. 




Deadline
Could you please make sure that these modifications are made on time to ensure that logging in is still possible with your application(s) from 1 May 2021 By starting implementation early, we can provide any required support if you have any questions or problems.









 
File Attachment 1 
File Attachment 2 
File Attachment 3 
File Attachment 4 
File Attachment 5 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255