Skip to main content

In this How-To article we explain how to use the Data Exchange Library (DEX) for OAuth2 authorization using either the Authorization Code flow or the Client Credentials flow. The article uses an example project that can be downloaded for replication and uses APIs from Google and Azure.

 

This article is part of a How-To series on the DEX. Let us know if you have any questions about using the DEX and/or suggestions for follow-up articles! 

Go to article: Using OAuth2 for API authorization with DEX

New to DEX? Start here!

@RoxannaBindenga is there any guidance for setting up redirect URLs for local deployments of AIMMS PRO servers? For cloud, it is pretty clear that we need to have the /extension//APPNAME]/oauth2/ redirect URL, but it is not clear if we need this for local PRO server deployments. 

Hi @MattC 

The same redirect URL is also supported for WebUI sessions running on PRO on prem servers since PRO version 2.41.1, see https://documentation.aimms.com/pro-release-notes.html#aimms-pro-2-41-1-release.

 

If you want to use OAuth2 Authorization Code flow from within WebUI sessions, then you need this redirect URL, as it is a necessary part of the Authorization Code flow. 

@MarcelRoelofs if I understand correctly, this means that it should be serverURL/extension/ … ? Just want to be sure. 

Reply


Terms & Conditions

Didn't find what you were looking for? Try searching on our documentation pages:

AIMMS Developer & PRO | AIMMS How-To | AIMMS SC Navigator