Visma Connect Authentication, can't get a token.

[pjleiwa]

I am busy to move from VNI to Visma Connect Authentication. Unfortunately I ran into an issue.

I've created a application with the following integration:

- vismanet_erp_interactive_api

This one is approved, and now I like to test it in Postman. When I do a request to get a token. I expect to get a login screen. But instead I get an error.  I based my settings on a post of Magnus Johnsen

(https://community.visma.com/t5/Forum-in-Developers-Visma-net/How-to-get-a-token-with-postman-using-V...). 

Does anyone have ideas to put me in the direction?

This is the reponse I get:

Ooops!

Something went wrong while processing your request.
We advise you to close the browser and try again later.

In case the problem persists, please contact your customer support and forward this error-ID 6b965240-e8ea-4d85-9b27-17e8b832ac5e so we can track the issue.

Visma status

Our status page shows the current status of Visma services. Visit to get the latest information.

Visma status page

Errorsettings in postman

[pjleiwa]

Hi Yildirim,

Thanks for your reply. The Debugger really helped me out.

[Yıldırım]

Hei, glad to hear ! 

[Yıldırım · Accepted solution]

Hello,

1) For the error IDs you receive, you can use OAuth Debugger.

Test and debug your OAuth requests by pasting in the Error-ID you may get during your implementation towards the /connect/authorize endpoint. From the My Applications page, you have access to the Debugger.

2) You can use Postman > Authorization to obtain token for the interactive flow. 

Auth URL:	https://connect.visma.com/connect/authorize
Access Token URL:	https://connect.visma.com/connect/token
Callback URL: Postman default	https://oauth.pstmn.io/v1/callback  (Add this to your Dev Portal > Application > Redirect URI

Name	Example value	Required	Description
code_challenge	The code challenge generated	yes, when PKCE enabled	Base64-URL-encoded string of SHA256 hash of the Code Verifier.
code_challenge_method	S256 or plain	yes, when PKCE enabled	Whether the challenge is the SHA256 hash of the string or the plain verifier string.
scope	openid email profile tenants vismanet_erp_interactive_api:create vismanet_erp_interactive_api:read vismanet_erp_interactive_api:update vismanet_erp_interactive_api:delete	yes	Identifies the user information that your application is requesting. One scope openid is required. The values passed in this parameter inform the consent screen that is shown to the user. Note: If your application is configured with Offline Access, you can include the offline_access scope to get a refresh token.

For more information: https://oauth.developers.visma.com/service-registry/documentation/authentication