Have you looked into the following documentation?

https://docs.ifs.com/techdocs/Foundation1/010_overview/210_security/030_authentication/oauth2.htm

Hi Asitha, 

Thank you for the reply. 

I already checked the f1 docs. 

The flow I am using is Authorization Code Flow and I managed to successfully obtain a token. The failure is resulted when I communicate with IFS APIs using the token. When investigated further on the error description (WWW-Authenticate header) it was bit unclear as the error messages mentions about id_token. 

As stated in the documentation, when tried with access_token the following response is returned

Bearer realm=<client_id>@https://login.microsoftonline.com/<tenant_id>, scope="openid", authorization_uri=https://login.microsoftonline.com/<tenant_id>, error="invalid_token", error_description="573fb18d-3879-400e-88ff-9c8a64ef1135: Signature of the provided id token could not be validated against the public signing keys of the identity provider."

When I send a request with id_token, I am getting the following response (WWW-Authenticate header). Which says that the issuer is not a trusted party. Am I missing any configuration?

Bearer realm=<client_id>@https://login.microsoftonline.com/<tenant_id>, scope="openid", authorization_uri=https://login.microsoftonline.com/<tenant_id>, error="invalid_token", error_description="3446ee2f-6e06-4726-9a20-63b698ca1636: The issuer claim of the provided id token indicates that it is not issued by a trusted party."

I am not sure if I am missing anything related to configuration.

With further investigation I managed to find the cause of the problem. My client application uses MSAL (Microsoft Authentication Library) to authenticate and acquire token for the user from Azure AD. The library by default uses Azure AD 2.0 endpoints. The tokens returned from 2.0 endpoints are not compatible with IFS Applications 10. Which resulted in the above mentioned error responses.

Solution

The solution was to change the scopes parameter to be compatible with Azure AD 1.0 endpoint. The following documentation details about using MSAL with v1 scope usage.

https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-v1-app-scopes

Based on this, the scope value “{client_id}/{oauth2Permissions_value}” is used (instead of “openid”).

oauth2Permissions_value: this must be obtained from the Azure AD application manifest reference. In my case the value is “user_impersonation”.

Thanks everyone 

With further investigation I managed to find the cause of the problem. My client application uses MSAL (Microsoft Authentication Library) to authenticate and acquire token for the user from Azure AD. The library by default uses Azure AD 2.0 endpoints. The tokens returned from 2.0 endpoints are not compatible with IFS Applications 10. Which resulted in the above mentioned error responses.

Solution

The solution was to change the scopes parameter to be compatible with Azure AD 1.0 endpoint. The following documentation details about using MSAL with v1 scope usage.

https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-v1-app-scopes

Based on this, the scope value “{client_id}/{oauth2Permissions_value}” is used (instead of “openid”).

oauth2Permissions_value: this must be obtained from the Azure AD application manifest reference. In my case the value is “user_impersonation”.

Thanks everyone 

Hi @avenash 

i have same issue & still not resolved. 

i’m getting token by using oauth2 successfully, & using that token but got 401 unauthorization while request some IFS API. 

can you share to me how you get the token & how to use that token to request IFS API ?

thank you.