I have a bot hosted in Azure which uses AADv2 authentication. The authentication was working perfectly until today, when it is throwing an error ("The resource you are looking for has been removed, had its name changed, or is temporarily unavailable") although I didn't change anything in the bot code or configuration.
I believe it is related with Azure rather than the bot's code since I test the connection from Azure Oauth Settings and it gives me the same error page:
"The resource you are looking for has been removed, had its name changed, or is temporarily unavailable".
This is where I test my connection:
I followed the instructions given by Microsoft to implement AADv2 in a bot:
Registered an app in apps.dev.microsoft as a Web Platform with redirect URL: https://token.botframework.com/.auth/web/redirect
Added OAuth Connection Setting to my bot
I believe it is not relevant, but just in case: the bot is developed with NodeJS using the BotFrameworkv4.
Everything seems to work fine now.
We didn't change anything in the code before or after the error and the authentication is back to normal again. I suppose it was an AAD internal error.
Microsoft answered the issue opened by #thomasmartinsen above, apparently there was a faulty service instance causing this problem, it is now repaired.
Related
Im getting below error(Img:1) in Web Chat channel after deploying the code, upto lastweek it is working fine but suddenly im getting the untrusted Origin error in browser console of Web App bot service and couldn't able to connect to the bot using "Test in Web Chat" feature. I have attached the Untrusted Origin error screen shot(Img:2) below. I am using .bot file as managing resource with Development and Production( Micorsoft AppId , App paswword, endpoint). I tried migrating .bot file to Appsettings(( Micorsoft AppId , App paswword, endpoint) as the managing resource but still getting the same error. Please help with the resolution for the error.
Img:1
Img:2
Here are the some of the resources need to check.
Kindly check the below points:
Check whether the messaging endpoint specified in settings in portal is correct or not. Please check with the path at the URL end (../api/messages)
Verify the bot configuration settings to check with whether using any incorrect APP ID and Password
The Messaging endpoint specified on the Settings page for your bot in the Bot Framework Portal does not begin with https or is not trusted by the Bot Framework. Your bot must have a valid, chain-trusted certificate.
Alternate Options:
Under 'TLS/SSL settings' --> set 'HTTPS Only' to 'On'.
For reference on similar issue kindly go through the below link:
There was an error sending this message to your bot - Test in Web Chat
I believe you have Enhanced Authentication enabled in the Directline channel and don't have the domain setup as a trusted origin.
https://learn.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-direct-line-3-0-authentication?view=azure-bot-service-4.0#security-considerations
I am trying to setup Web Security Centre for my Google AppEngine App.
I tried using Google as well as Non-Google Account for Authentication where I provided Username and Password but it errors out saying
Could not sign in using the provided username and password
I tried below things:
Tried creating a test account vikash-security#gmail.com (in compliant with google naming convention) in my gmail and using the same for authentication. (this user had same domain name as my company's)
Created a test user with different domain name and used it for the authentication.
Both the above users have access to my Google App.
Both of the way did not work and throws the same error. Can anyone help me out with the same?
Google enforces a real name policy on G+ accounts. Your test account may be blocked from G+ if the name does not look real. at [1]. It will only work if the Google account you provided should have been G+ verified (with proper G+ setup), but still need to retry after the first failed attempt and it eventually will work.
There are few issues related to this and if this is a bug it will be resolved soon.
I raised this concern with the Google support team and got to know that there was issue from their end and they got this fixed and now my web security custom scan is working with non-google authentication.
I am trying to call the rest service for getting idToken from Azure B2C application using following URL:
https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token?p={POLICY}
I am passing all the required parameters in the payload :
grant_type=authorization_code&client_id={ClientID}&scope=https://{tenant}.onmicrosoft.com/api/read openid offline_access&code={AUTH_CODE}&redirect_uri={REDIRECT_URI}&client_secret={CLIENT_KEY}
The same approach is working on one environment but returns
404 : The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
when accessing from another environment.
What am I missing here? Any Azure configuration that I need to check?
Your request looks good. So the key point of this issue should not be in B2C side.
This error generally means that the file you are looking is not present on the server or web.config file is not configured properly.
As the approach is working on one environment but failing for another, you should check the web.config file which is in the failing environment to see if it is configured correctly.
See a similar question here.
I have implemented AAD authentication in one of my webapp, using OWIN. everything is working as expected on dev environment but it is not working on PROD. At login it goes to AAD page, it authenticate users and it redirects back to my registered page, but register page is not opening at all. In title it show working only. I am completely lost, how to resolve this, Please help me to resolve the same.
Thanks in advance!
I got the solution for this. The issue was - to store the Tokens the Owin context created a local db (AzureTokenCache.mdf and .ldf files) in App_Data folder. This uses SQL express. Now we all know that using PaaS we cannot use any Software. Hence my authentication failed every time saying that error connecting to database. I moved everything to SQL Azure and it worked for me.
I'm using Azure Active Directory B2C with ASP.NET Core, when I click the sign-in it works like a charm on my local machine but when I deploy my web app in Azure it only works with Edge.
With Chrome and Firefox I always have this error:
I am creating a new web app (social network) and I need to be in beta for November because we go to the show in Toronto related to healthcare.
So to manage all the users (creation, login) I use Azure Active Directory B2C.
When I create the user I use the graph API because I need to do some stuff in my workflow but this part works fine.
After this I created my sign-in policy and I customized my branding.
The first problem I have is the password field, how I can place a placeholder there? (see attached picture).
The second problem I have, when I click the login it works #1 in Edge but in Chrome and Firefox I have this error :
An unhandled exception occurred while processing the request.
InvalidOperationException: Invalid non-ASCII or control character in header: 0x000D
Someone got this before ?
I faced the same issue. However, i tried to first "sign up" and then sign in. This resolved the issue.
It's not related to a specific browser and can be reproduced on any oh them with the good repro scenario. I guess your issue is that you try from an HTTP website. Since AADB2C will redirect to an HTTPS page, thus the headers are not well managed and you get this error.
Enforce the https on any website using B2C and you may solve this issue