You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for making this solution available!
I've deployed the solution, tripple checked everything and as far as i can see haven't mixed up any app ids,clientid's , secrets etc. App is configured to use the Delegated permissions, admin consent has been given.
Googling led me to a few posts that suggested ticking the checkbox for an implicit grant of ID Tokens under the authentication settings of the Qbot-api app registration. I tried this, and got me one step further (or farther away). After signing in on the dashboard it now gives the following error: There was an error initializing the Bot serviceResponse with status: 0 for URL: null .
Any ideas or things that i should check?
The text was updated successfully, but these errors were encountered:
Hi,
First of all, thanks for making this solution available!
I've deployed the solution, tripple checked everything and as far as i can see haven't mixed up any app ids,clientid's , secrets etc. App is configured to use the Delegated permissions, admin consent has been given.
The dashboard app loads in Teams and shows the Sign In message. Signing in however resulted in a warning (AADSTS90002: Tenant 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx' not found. This may happen if there are no active subscriptions for the tenant. ) . The url it redirected to was https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx/oauth2/authorize?response_type=id_token&client_id=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx&redirect_uri=http%3A%2F%2Fhhs-qbot-questions-tab.azurewebsites.net%2Fapp-silent-end&state=fec80d89-ae0a-4cc5-bc4d-1dcfd7cef76b%7Cxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx&client-request-id=eaebf59c-044d-475e-8058-547bbf746403&x-client-SKU=Js&x-client-Ver=1.0.17&prompt=none&nonce=36ccd3a5-2a6e-4d27-90e5-f683fea845bf&iframe-request-id=f224beaf-bde6-4b43-9c42-e01200224e00
Googling led me to a few posts that suggested ticking the checkbox for an implicit grant of ID Tokens under the authentication settings of the Qbot-api app registration. I tried this, and got me one step further (or farther away). After signing in on the dashboard it now gives the following error: There was an error initializing the Bot serviceResponse with status: 0 for URL: null .
Any ideas or things that i should check?
The text was updated successfully, but these errors were encountered: