Hi again!! Im having some troubles with the Firebase OpenId Authentication, when I set it up works fine, my user is saved in the database, but after some time this connection between firebase and 8base just stops, and the users are saved into firebase but not into 8base then I need to either create a new Auth profile or “edit” the old one with the same info that was before.
Thanks as always!!
Hello Gabriel!
I’ve got your issue. I’ll give you a response soon.
Lada Kokotova | Technical Support Engineer
Hi,
We are seeing the exact same issue too. Look forward to hearing your response.
Thanks,
Matt
If it helps, when I inspect the XHR request I receive the following error: “Unknown iss claim in authorization token. Unable to find authentication profile with discovery endpoint https://securetoken.google.com/example”
Hello @gabriel.espinoza!
We are reviewing the logs from your workspace at the moment.
Did you use https://github.com/8base/8base-firebase-auth-example/tree/master/client for firebase auth or implement it differently?
Lada Kokotova | Technical Support Engineer
Hi Lada!! yes exactly, we used repo since in the 8base docs the process is not clear
Hello Gabriel!
We’ve discovered the problem with caching/updating Google public keys used for parsing id token on our side.
To make it short: public keys are being refreshed, but we don’t update it and get cached one. So when you update your authenticationProfile we get a new one.
Here is the link for public keys:
https://www.googleapis.com/robot/v1/metadata/x509/securetoken@system.gserviceaccount.com
The temporary workaround for you till we fix the issue: trigger authenticationProfileUpdate mutation when you get following error
Unknown iss claim in authorization token. Unable to find authentication profile with discovery endpoint
We’re working on fix. We’ll definitely let you know when it’s ready.
Lada Kokotova | Technical Support Engineer
Quick update. We have engineering looking into this next week. We’ll look to get it resolved, tested, and released ASAP. I’ll post back here with udpate.
Thanks, Tim
@gabriel.espinoza Since we haven’t heard back from you we’re assuming this workaround worked and we’re going to put the permanent fix in one of our upcoming releases.
Hi Timothy,
Thanks for looking into this. When can we expect the permanent fix to be released? I’m still having this issue, the only way around it for now is to update the Authentication Profile when it’s not working.
Hello @mattevans,
Fix will be released in two weeks. We’ll let you know when it’s ready.
Lada Kokotova | Technical Support Engineer
Hi all! i manually was updating the OPEN ID profiles, is the bug fixed?
Thanks!
Awesome!! thanks a lot !!!