SSO configured as per docs and API works fine on Postman but only gets errors on the actual app and emulator - buildfire

Using this (https://github.com/BuildFire/sdk/wiki/Using-Single-Sign-On-(SSO)), a WordPress-based OAuth server and using Postman as well to make sure that the API is responding as expected. I even went so far as to whitelist the specific URLs from the firewall.
I'm only seeing a generic "Error while testing SSO Login" in the emulator and on the actual app, we get "Invalid Login" errors.
Using the same credentials in Postman works as expected.

Related

Auth0 callback not working after deploying on Heroku

I build a webapp that uses auth0. Locally everything is just working fine, but after I deployed the app to Heroku the auth0 callback is just not working and gives me a ERR_CONNECTION_REFUSED
So here is my setup:
Auth0 Services is subscribed in Heroku
Callback-Url in Auth0 is set to http://localhost:3000/callback
/callback route is implemented (just a simple 200 response if it works)
My guess where it fails:
In the Auth0 logs I shows a successfull login and the browser redirects to http://localhost:3000/callback instead of the Heroku-URL. So it seemes to me that there is some kind of redirection missing.
Any help on this topic would be nice, since all the blogs and help-pages didn't help so far.

JWT token in Blazor App Page needs to be loaded twice to validate token

I have a Blazor server application with JWT authentication. The application authenticates using a JWT token in the URL. The applications runs successfully in debug mode under localhost locally without any issues.
When published the application to Azure service the following happens:
Go to google or any website
Paste url with token
It doesn’t validate the token and redirects to the error razor page
Paste same url again and it works completely fine and loads correctly
As it’s not happening in debug mode on visual studio not sure on the best way to debug this? Or why this could be happening?
You could have an issue with CORS? Does it work if you go through the normal authentication flow on the app? E.g., using incognito browser, open Azure app, you are unauthenticated so you get redirected to login, after login you get redirected to app again?
If that works, you are having issues with where the request is coming from (possibly). There really isn't much info to work with here - can you update with browser Developer Tools console output/network tab and then the server logs?

Azure AD b2c android app to access non-Graph API securely

I am trying to access an API on the same server that my android app is registered. The process of logging into the android app works fine. I have attempted to use the IAuthenticationResult.getAccessToken() generated to access an API on the same server unsuccessfully. I get a 401 Unauthorized error message both on Postman and my application. The sample applications available work fine with Microsoft Graph but I haven't seen any sample accessing other forms of API including those hosted in the same client.
The solution that worked for me is specifying the SCOPE parameter in the android code as {"https://graph.microsoft.com/.default"};. That was the only way I could obtain a valid bearer token that could be validated on the backend by calling https://jwt.ms/

Azure Bot service talking to Azure Logic App - 401 unauthorized

I have an Azure bot which is all developed and working fine. It currently talks to a 3rd party workflow application via a simple webhook.
I am now trying to replicate this using Azure Logic App. I have a simple logic app that responds fine to requests from POSTMAN. However, when I set the Messaging Endpoint in the Azure Bot service to the URL of the logic app's top node (when a http request is received), I see 401 unauthorized responses from all of my channels in the bot and I don't know why. POSTMAN is using the exact same target URL and works fine.
Any ideas what is going on here?
I had a similar problem, and found the solution was to first ensure an Authorization header is being sent, and 2nd, set the value to null.
Refer: https://learn.microsoft.com/en-us/outlook/actionable-messages/security-requirements#action-authorization-header

My bot works fine in the emulator,even with Microsoft app id and password but when I'm testing it online it fails

My bot works fine in the emulator, even with Microsoft app id and password but when I'm testing it at https://dev.botframework.com I get a message
couldn't send message retry
I get a
401 unauthorized
error when I'm trying to get a reply from the emulator with bot url https://botwebdeployment.azurewebsites.net/ (deployed in azure).
I have added my bot bot in Microsoft bot directory and have enabled Skype, but even on my machine I can send message on Skype app to bot but I don't get any reply.
Verify application settings - confirm you've updated the Microsoft App ID & Password then deploy to Azure again.
Verify HTTPS endpoint - In the dev portal (https://dev.botframework.com), settings page; make sure you used HTTPS instead of HTTP.
Reference: https://learn.microsoft.com/en-us/bot-framework/deploy-bot-visual-studio

Resources