403 disallowed_useragent solution for website, android and IOS app - asp.net

I have created an ASP.NET website by selecting a template in visual studio and got open authentication already configured, I just un commented some code and created client and app secret for google and facebook and I got authentication working fine.
Authentication is working fine for website and now I have created an Android and IOS app in Xamarin, I an using web view but google authentication has stopped working, I am getting "403 disallowed_useragent" which is a known issue now. facebook authentication is working fine.
I have temporarily disable open authentication on my website, what are the options available now?
I am looking for a solution that works for website, responsive website on a mobile browser, Android and IOS app.

Related

Getting 'The application is disabled' for LinkedIn app and app disappeared from LinkedIn developer My App list

We had created 2-3 apps in LinkedIn developer account and used it in auth0 tenant, suddenly we are getting message -
"The application is disabled".
And now there is only one app, can any one please suggest where apps gone away and why? How to republish those apps again?

PWA with Windows Authentication

On the high level, I have a PWA with React frontend and .netcore backend. I use service worker for caching and offline ability, in conjunction with workbox plugins for some precaching feature.
The app uses Windows Authentication. Which works fine if it wasn't a PWA app. It also works fine the first time the PWA app launches, I get the username, password login popup.
However from the second time visiting the app, it wouldn't show the login popup, the app fails at pulling data from the backend because it is unauthenticated. One weird behavior is that, if I open Chrome Dev Tools(by F12), then the login popup immediately shows up.
I thought it's caching related and somehow the service worker interfered with the server side authentication workflow. Maybe because the index page is cached by the workbox precache plugins, and it did not cache with the fetch header of 'credentials': 'include'? I tried adding the fetch option to other api routes, which are cached by workbox plugin RegisterRoute. However I didn't find a way to add it to the precacheAndRoute(self.__WB__MANIFEST). Wondering if that's the problem. But I'm also not sure why having Dev Tools open would trigger the popup to display.
Any input is appreciated.

In App Browser open link in new tab in ionic 3 PWA

I am using ionic 3 PWA on my website. It is an app for woocommerce. I use in app browser to complete payment inside my ionic app. Everything works fine when running the app on android or ios. But when I use the app as PWA or web app in the app browser, Open the required URL in a new tab which should not happen as in app browser officially supports browser.
Please help with any solution or workaround.
Did you try, to open URL with blank in app browser
InAppBrowser('url', '_blank');

Can I use Firebase Dynamic Links for a web app?

I don't see any option for Web under "receiving dynamic links" in Firebase Dynamic links page.
Without the SDK, there's no way to connect a post-install user with a pre-install click.
I have a desktop app that runs on node.js like a web app, using nw.js. What I'm trying to do is create referral links for users. After someone clicks a referral link, I need to be able to track his referrer. But the problem is that link is only going to take him to the download page, after he downloads and opens up the app for the first time, how can I reach his referrer info? The desktop app has no connection with the website that users download from.
I understand that this can be done with Dynamic Links SDK but can I use that SDK in a web app?(desktop app actually but runs with HTML/node.js)
The post-install deeplinking in Dynamic Links is just for Android and iOS - so there isn't an equivalent for a desktop app.

Auth0 Authorization Stops Working When API is Published (.Net Web API / Angular)

I am currently using Auth0 with Loc7 in Angular and an ASP .Net Web API v2.
The project works fine locally. The user can log in using the widget and the API sees the User as authorised with no issue.
When the app is published the API returns 401 unauthorised when a call is made.
There is no issue with Angular app no matter where on the web space it is placed so I do not believe it is an issue with the Allowed Callback URLs in the Auth0 dashboard.
The config works fine locally and there are no major changes when being published except the database connection string.
The database is an exact copy of the local database.
The API MVC Template works fine but does not do anything aside from load and show routes. I have not changed the template since it was generated.
There are no errors on the server.
The API is in a newly created app directory on the server.
Auth0 Dash reports the login from the Angular code successful. The profile is returned with a valid token viewed through the dev console.
Has anyone else had a similar issue? Could this be an issue with how the hosting is set up?
Happy to post more info, I am not really sure what to post it is a fair amount of code.

Resources