I am developing an app which utilizes Deep Search on a data container in Veracity. The app is already registered to access the data fabric. I can currently acquire a token with MSAL using the Veracity Data Fabric resource URL as the scope, however this same token does not work when calling the Deep Search API (401 error). How can I obtain the correct token for Deep Search authorization? We think that either a particular Deep Search scope is required in the token request, or that the app needs to be registered to query Deep Search.
Any assistance as soon as possible would be greatly appreciated.
The refresh_token grant type could be used to acquire access token for different scope. With .NET just call ClientApplicationBase.AcquireTokenSilent with the Deep Search scope you need. Make sure that you request the offline_access scope to get refresh token and you store it. If you use Veracity.Common.Authentication.AspNetCore it should be sorted.
Your client application should be configured to get the access token for the scope. I’m not sure about Deep Search but in general you should have it checked in your Veracity for developers > Client App > Advanced tab > API access section. If it’s not there you need to request it giving your APP ID. You could quickly check if you can get the access token by temporarily changing the scope you get on log in with the Deep Search.
I did not found any recent nor accurate documentation of this feature that is called Multi-Resource Refresh Tokens. But it works with AD B2C from Veracity.
7 Likes
Thanks Damian. We are still looking to resolve this question, we think our problem stems now from a combination of our client application not being registered to access the Deep Search API and not currently having access to the relevant scope from which to obtain an access token. Can Veracity provide support to access these?
Hi Matt,
thanks for reverting back to us. We are looking into it and will get back to you as soon as we can. Thanks for your patience.
Andreas
1 Like