As part of the cloud migration, we created an app-service and deployed the API that would connect to the IFS database. Even though the AA’s Azure IPs are whitelisted in the IFS side, still we are having issues connecting to the database. The attached screenshot shows that we are able to establish connection to the IFS servers from the Azure App-Service. However, when we try to invoke an API that connects the IFS DB, the API fails to connect to the DB. Attached is the stack trace of the error that we receive from the IFS dll. Could you please point us to someone from IFS who can help with this and make us understand what could be causing the issue.
Using POSTMAN I am able to obtain a Token.I paste the id_token in the access token location POSTMAN.When clicking the Send command I receive a 401 error:WWW-Authenticate: Bearer realm="d9e03690-59a1-453d-8439-8f9363f4eb30@https://login.microsoftonline.com/49793faf-eb3f-4d99-a0cf-aef7cce79dc1", scope="openid", authorization_uri="https://login.microsoftonline.com/49793faf-eb3f-4d99-a0cf-aef7cce79dc1", error="invalid_token", error_description="f5d5fc6e-8e49-4846-93b4-1c74ed8ad50f: Signature of the provided id token could not be validated against the public signing keys of the identity provider."We use SSO with Azure AD. I am using a functional user that has admin permissions when answering the IFS authentication challenge, when acquiring the token. This functional user is not part of the Azure AD but I can sign into IFS as an admin using this users credentials.I’m not sure how to use any other user due to the directory id and/or PW for SSO?All help is appreciated.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
