Xamarin iOS Xamarin.Auth Keeps Account data even after uninstalling the Application - xamarin.ios

To save user auth credential i've used Xamarin.Auth Account store
But it keeps the credentials data even after i uninstall application
so the problem is when reinstall new version it would automatically gets logged-in.
How can i clear auth credentials on uninstalling applcation ?
Thanks in Advance !

Related

Firebase Authentication create user

I want to programatically add new users in firebase auth service with phone no and email (both providers attached to each other). Is there anyway I can do it without verifying them and maybe through nodejs (reactjs will also work, but node is preferred as I building an api to do some custom task after user is created) ?
The above issue is resolved by: https://firebase.google.com/docs/auth/admin/manage-users#create_a_user

How to persist device id or any id after extension is re-installed

I have a browser extension which stores a client-id in local storage upon installation in background.html page. Now if i reinstall the extension the client-id is gone from the local storage of background.html. So i need some implementation such that either that id can persist on re-installation or if i can store the browser id or something as such in my database and check with that on re-installation. Can anyone help me on this?
I tried using cookies and cache storage its not working for me.

Nuget manager not prompting credentials while connecting to artifactory

I am using VS2017, when i tried to open Package manager and selecting Artifactory as package source its not prompting for credentials and returning
[Artifactory] The V2 feed at 'https://itec-artifactory-.....' returned an unexpected status code '403 Forbidden'.
I tried clearing nuget and browser cache, but it didn't work.
The same scenario in VS 2013, its prompting for credentials and connected successfully.
Any help is appreciated.
Reset the Nuget artifactory credentials. They are stored in Control Panel -> Credential Manager.
Go to Windows credentials. Remove with "VSCredentials_" prefix.
Restart VS.

Azure active directory (AAD) authentication, redirect URL not working

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.

Sign-in Provider Issue While Using Third Party Auth With Firebase v3.3.0

I am having a puzzling issue with third party (Twitter) sign-in to my Firebase instance. I get the following exception when trying to authenticate via signInWithPopup JavaScript method:
The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth section.
I have confirmed that Twitter sign-in is indeed enabled in the Firebase console:
I have read various blog posts stating that Firebase users have experienced issues with third party auth when using v2.x.x of the Firebase SDK when having their projects created in the new console (subdomain of Google). However, I don't think these conditions are applicable to my situation because:
My Node project is using Firebase v3.3.0 npm package and I haven't found anyone else complaining about third party auth while using this version.
I created my Firebase project using the new console.
Other things that may be useful to know:
I can read/write data from/to Firebase without any problems
I have not tried any other authentication methods
Great thanks to whoever can shed some light on this issue :)
I ended up fixing this issue by creating a new Firebase instance in the old console and then porting it over to the new console. My only assumption is that the authentication problems noticed with v2.x.x versions haven't been fixed with v3.x.x :(

Resources