Firebase suddenly reports invalid signature - java

We are current hosting a Java/Spring server including firebase ID token verification on SAP Cloud Platforms (Hana Cloud). The authentication worked fine for the last few month, but suddenly stopped working yesterday, then it recovered after ~30 minutes and today it suddenly stopped working again. The error always is:
java.util.concurrent.ExecutionException:
com.google.firebase.auth.FirebaseAuthException: Firebase ID token has
invalid signature. See
https://firebase.google.com/docs/auth/admin/verify-id-tokens for
details on how to retrieve an ID token.
It is still working fine when i test it locally. What could cause this error in this unpredictable way? Are there request limits on the firebase-backend regarding Id token verification requests (which would still be strange, because other times it worked under heavy load just fine)?
Any ideas what might be causing this? I could not find really anything regarding this error.
Thanks!

It appears that there indeed was a server configuration problem with the root certificate. Sadly i cannot give any specifics, because i don't have direct access to the server and only the information the system admin gave me.

Related

Failed to retrieve JMX service url when attempting AWS/mySQL DB connection via intellij

I've made the leap towards learning AWS and unfortunately have hit an impass, it would seem.
When attempting to launch my application, I'm receiving a notification of
"Failed to retrieive application JMX service URL".
The peculiar thing about this is, my connection is successfully authenticated via AWS and Workbench, however when launching the application it's seemingly attempting to connect with a different usernam specified in appliation.properties or anywhere else for that matter.
Although not good practice, I've been attempting to connect via my admin account through AWS which is further mirrored within workbench, however the error returned is specifying my IRL name which isn't specified anywhere other than the "Remote Management" panel in DB connections within workbench.
This being SSH connectivity url, which is specified never to be used.
I'm unsure whether or not this is where it's being read from, although certain it's the only place being referenced.
I've made an attempt at disabling this, which it currently is - Still reads the same name.
I've made attempts at creating and granting authorities to a user of this username within my DB and still no avail.
java.sql.SQLException: Access denied for user 'removed for safety' (using password: YES)
The above is the error returned, which again specifies a username not declared anywhere for use (other than SSH remote management which is unused) and an IP address which is unrecognised.
Following creation of a new user within both AWS and mySQL DB the error message changes to the following:
java.sql.SQLException: null, message from server: "Host' is not allowed to connect to this MySQL server"
Any help would be greatly appreciated as I've now tried everything within my currently limited knowledge base.
Attempted configuring user within AWS and mySQL matching credentials attempting access - Hoping authorisation would be granted, although simply changed the error message.
Conducted research, although not coming across anything related to AWS/mySQL connectivity related, or varying issues.
I rebuilt both mySQL and AWS in the exact same way and it's now working.
Unsure as to what or why, but there's quite literally no amendments in settings, or code for that matter.

How to solve 413 request entity too large

When I post a form with an image taken from my phone I reserve the error "413 request entity too large" I realize that an image included in the form taken by the phone camera is too large, and the server rejects the request... but how can I fix this issue, I'm using Java Spring framework, and MySQL database, all of this handled with Amazon aws services.
You have to modify your .platform as shown in the docs.
For example, you could have the following .platform/nginx/conf.d/myconfig.conf with content:
client_max_body_size 20M;
I struggled with this for so long until I came across this post:
https://medium.com/#robin.srimal/how-to-fix-a-413-request-entity-too-large-error-on-aws-elastic-beanstalk-ac2bb15f244d
Couple things to watch out for here, if your server is restarted or you deploy a new version etc, then your nginx server will also reset and you will need to perform these changes again. Also periodically, AWS seems to reset your EC2 instance address, not sure why, but you need to perform these changes again afterwards. There must be a way of making these changes permanent but I haven't figured that part out yet.
I find the solution thanks for helping...
1-I connect to my EC2 instance throw the "connect" button, a terminal appears.
2-I edit this file: etc/nginx/nginx.conf
3- Add this line:client_max_body_size 10M;
and it works fine.
thank you all ;

Unable to resolve host: No address associated with hostname

In my Android application I use my Rest API, delivered via the cloudflare network (with active proxy). Very often the first connection to the okhttp API receives the following error:
Non-fatal Exception: java.net.UnknownHostException
Unable to resolve host "mydomain.com": No address associated with hostname
After the user retries one or more times, subsequent connections are successful. If there is some downtime with API requests, the error is likely to occur again.
I cannot understand what causes this problem. If it can depend on cloudflare or if there is a way to solve on the okhttp side.
do you have any ideas?
I had the same problem with one of my crypto wallets only to discover my app needed to be updated and once I updated the app everything was smooth from that point on. When I first went to the Play Store to see if I had any updates due, there were none but when I searched specifically for my wallet app in the Play store an update was needed. So make sure you search for the specific app that is giving you the problem in the Play store.
Or you have no internet on the device
or you forgot to add
<uses-permission android:name="android.permission.INTERNET" />
permission in manifest.xml
#see this thread
I have also the same issue but after restarting android studio it solved my problem.

BillingClient: getSkuDetails() failed. Response code: 6

I've integrated Google inApp billing in my android App. It was working fine, But now I noticed that on one device its always returning BILLING_RESPONSE_RESULT_ERROR response. In Logcat it shows following error.
BillingClient: getSkuDetails() failed. Response code: 6
I couldn't find any help regarding this issue, Can someone help me what could be the possible problems and solution. Thanks.
This generally happens when you have signed out from Google account in your device. All you need to do is just sign in again, if needed do a full restart.
Well, my situation is the connection between my device and google's servers is unstable.Try to open the GooglePlay,and check if the connection is healthy.And it wroks.
In my case, this happened when a new app I submitted was in "Draft" status, not yet approved by Google. Just wait until it's approved and payments will start to work.
An alternative would be to submit it in the internal track and add the email for you play account as a test user.

I have some problems using my app for the second time

I have developed an app using Android Studio, which include login and register activities. when I copied my code to my new computer I have launched the app for the first time and it worked just fine. The day after, when I was trying again to launch the app once again. I wasn't able to sign-in to an existing user. I even could not create a new one. Does someone have any idea what caused it' and how could it be fixed?
Your question has no details at all..
Do you store the user credentials on a db?(it could be that you cannot login because you didn't connect correctly to the db) which type of db? is a Web service to an admin panel or some code posted on a hosting/vps?
Find out which is the error inside the logcat and post ONLY the error, maybe the stacktrace can help you.
So you can launch the app but the data inside is missing(credentials).. Do you see everything as usual or are there any images/details missing?
Stupid but easy to forget: do you have an active internet connection on the emulator?
have you tried to debug the code, have to tried to debug at least the authentication/register process?
Add more details, check your manifest is ok and you have all the permissions(internet, wifi or anything else), post the logcat error(if there is an error) or post the debug error, then someone can answer

Categories

Resources