Thanks James! That worked. Did some more testing and for the API permission you only need the “User.Read”.For the Token Configuration you don’t need the email ID/Token claim in Azure AD. And last, the scope can be only “openid” in IFS IDP configuration. Seems the attribute claim in IFS “email>email” and “User.Read” is all it needs to get the Email value from Azure and connect it to the ID Identity in IFS. /Jacob
Hi Sajith,We use Azure AD as IDP. It seems like you say we miss some information regarding the user in the token. Do we use ID token or Access token?So far we have only configured Azure AD SSO as we would with IFS10 but with the difference being the URL. See picture below.We also tried a few more claims other than default values, see below: Lastly is there something we need to do with Attribute Mappers? We cannot find any documentation regarding it and if we try configure something here we get http error 500.
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.
