Door deze website te bezoeken maak je automatisch gebruik van cookies.

Als de browser instellingen niet veranderd, dan maak je gebruik van de cookies. Lees meer

Sluiten

2BA Cookie informatie

Deze tekst is van toepassing op de 2BA sites "Homepage", "Unifeed" en "Bestand & Beheer".

Wat is een Cookie

Wij maken op deze website gebruik van cookies. Een cookie is een eenvoudig klein bestandje dat met pagina’s van deze website wordt meegestuurd en door uw browser op uw harde schrijf van uw computer wordt opgeslagen.

Soort cookies

Wij gebruiken cookies om het gebruik van onze site faciliteren, het inloggen te onthouden en t.b.v. snelheidsverbeteringen. Daarnaast gebruiken wij (anonieme) gegevens voor het opbouwen van site statistieken zoals het aantal keer dat de sites bezocht worden, met welke browser etc. De 2BA site kan niet zonder cookies werken. 

2BA maakt geen gebruik van tracking cookies t.b.v. advertenties.

 

 

Documentatie

For the security of our products (Unifeed, Webservices), we use the open standard OAuth2. The OAuth2 standard is a widely accepted standard that is used by many software parties and has an abundance of libraries available. With the OAuth2 autorisation protocol, it is possible for third-party applications to acquire limited access to our http services. To access these services, the application needs client-credentials (client_id/client_secret). To gain access to the data, the user additionally needs to be identified by his/her username and password. More complete information about the OAuth2 specification can be found here: OAuth2 website

2BA supports 2 authorization flows from the OAuth spec. These flows are: "Resource Owner Password Credentials Grant" and "Authorization Code". 

Steps:

  • Choose one of the supported flows. Choose the flow that best matches your situation.
  • Use these flows to retrieve the Access Token / Refresh Token one time.
  • Refresh the Access Token, if expired, by utilising the Refresh Token.
  • Invoke the desired JSON or SOAP service or Unifeed and provide the Access Token.

Resource Owner Password Credentials Grant

This flow can be used when there is a trusted relation between the application and the end user. The end user enters his/her username and password in the application. This flow can be used, for example, when the application is installed on the end user's computer.

More details and example code can be found here: Resource Owner Password Credentials Grant.

Authorization Code

This flow can be used when there is no trusted relation between the application and the end user, for example, when the application resides on the internet. The user will, in that case, NOT enter their 2BA credentials in a third-party application. The application can use this flow to redirect the user to the 2BA website, where the user will enter his/her credentials and 2BA will return an autorization code to the third-party application.

More details and example code can be found hereAuthorization Code

Parameters

Authorization URLhttps://authorize.2ba.nl/OAuth/Authorize
Access token URLhttps://authorize.2ba.nl/OAuth/Token
Client ID(as received from 2BA)
Client secret(as received from 2BA)
Preferred grand typeAuthorization Code