Hello, Just trying to use the OIDC integration with Azure. Whilst most of the steps documented for Google OIDC integration should in theory work, it appears that the Azure Integration does not access redirect URIs that have a paramter in them.
The redirect URI provided by Intella when a new integration is created has the following parameter in it: http://x.x.x.x:9999/login/login.html?provider=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
To what extend can you push an update where the parameter is not required for us to be able to integrate this with Azure OIDC.
OAuth Single Sign On
in Intella Connect/Node/Investigator
Posted
Hello, Just trying to use the OIDC integration with Azure. Whilst most of the steps documented for Google OIDC integration should in theory work, it appears that the Azure Integration does not access redirect URIs that have a paramter in them.
The redirect URI provided by Intella when a new integration is created has the following parameter in it: http://x.x.x.x:9999/login/login.html?provider=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
To what extend can you push an update where the parameter is not required for us to be able to integrate this with Azure OIDC.
Thanks.