I have an app using the Firebase integration as described here: https://sdk.buildfire.com/docs/firebase-integration/
When I use the integration token to create a custom token and then login to Firebase, I get an error saying Invalid Integration Token. I have verified that my database name is correct. I have tried both Firestore and Realtime Database integrations and have the same issue.
When I create the same integration token with Development Mode checked, it works in my web-based apps (e.g. hosted on app.buildfire.com) but I get the same error when trying to login from my app on my phone.
Any tips on how to fix this? I have an old integration token that I made months ago that works ok, but I am using a different Firebase account for our production environment and need a new integration token.
Related
I am researching the feasibility of porting an existing Vue 2 app to be an Azure Static Web App (SWA). A requirement is the ability to run the Vue app locally and authenticate against our Auth0 tenant to retrieve a access/bearer token to send along with our HTTP requests.
It appears that a SWA can utilize custom authentication (Auth0), and I was able to complete that successfully by following this article. However, I'm not seeing any information around capturing the access token. There is an /.auth/me/ endpoint which has user information, but that does not contain the access token:
I also looked into the Azure Static Web App Emulator which allows for defining an identity profile when running locally, but I'm not seeing a way to specify an access token here either.
Is it possible at the moment with a SWA to obtain an access token using a custom auth provider when running locally and when published live?
Managed Authentication in Azure is really only useful for fairly simple use cases. I think you're going to want to implement your security directly inside your Vue application.
https://auth0.com/docs/quickstart/spa/vuejs/01-login
You mentioned needing an access token but didn't say where it comes from or what you're doing with it. Are you trying to call an Auth0-secured API?
https://auth0.com/docs/quickstart/spa/vuejs/02-calling-an-api
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/
I am trying to login clients using their email and password through Auth0 with a Node.js backend on the Azure app service and a Xamarin.Forms client. The problem is that I can't create a custom authentication on Node.js since the tutorial I was following used a .NET backend. I also followed this tutorial for Node.js backend both by the awesome Adrian Hall, but it seems to override the already exisiting Facebook login system, and I can't find enough material on that problem. Is there any other tutorial on doing that or am I getting something wrong?
You are doing something wrong. You can use Auth0 with no problems - Auth0 will be used for all the providers, and their client SDKs will allow you to choose Facebook, Google, Username/Password or anything else you need.
The mechanism for the process is as documented - I think you just need to re-read the blog post and understand the transaction - you use the Auth0 libraries to get the Auth0 token, then submit your Auth0 token to your custom login API (/.auth/login/custom) to mint an App Service token that is used by the Azure Mobile Apps client SDK.
I have an application that uses the DocuSign API (the NodeJS SDK, specifically) and got everything working perfectly on the demo sandbox. The Docusign people certified the app for production.
I followed the "Go Live" documentation and changed the endpoint from https://demo.docusign.net/restapi to https://www.docusign.net/restapi in my apiClient.setBasePath(), however, I'm getting a USER_AUTHENTICATION_FAILED error.
The username and password have been set to the same as on the demo sandbox, so I know they are correct. Also the IntegratorKey is the same as the demo sandbox, and after they certified the app, I can now see it in my production account.
Here is a pastebin of the error
Any assistance would be greatly appreciated!
This is most likely a baseUrl issue, you should be parsing the baseUrl that is returned in the login API and using that as the base for subsequent API requests in production.
In your developer sandbox (ie demo) environment all URLs start with "https://demo.docusign.net/" which is why all your test calls work in demo, in the live production system the account URL will vary based on user and which data center their live production account resides on.
You need to parse the baseUrl value that is returned from the Authentication:login API and use that as the base for subsequent DocuSign API requests, or use the base_uri value if using OAuth.
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 :(