-
-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to create DEFAULT_TOKEN #46
Comments
@anhnt0212 same problem. Have you any solution? |
@ktamas77 @llbbl @brianpilati @craigrusso can you help ? |
@greabock i don't have :( |
Can you help me ? On Mon, Aug 22, 2016 at 6:18 PM, Parth Dabhi (iOS & Android developer) <
|
@skizzo tks a lot.let me check again :D |
Does this database secret override all the security rules defined? |
@martisj i think it no |
yes the secret still works but it is deprecated. you ought to be using Service Accounts now but this library does not yet support it v1.x/2.x Firebase JWT token's that @anhnt0212 is using are not the same as the secret. you could try kreait's version instead, which supports the Service Accounts used by v3.x firebase having looked at that codebase, it's not simple so it's no small task that we are asking @ktamas77 to do to update this library to the new version by the way what are you actually trying to do @anhnt0212 ? |
ps if you use REST to access Firebase .json I believe authentication works in either of the following ways
I believe the middle one is what the token generator library you are using provides @anhnt0212 as you can see the token is passed in the querystring options for you could try creating a JWT token with Firebase token generator using your secret, and then pass that token into @ktamas77's library... if you don't want to pass your secret directy. I've not tried it though. it depends if it should be passed as auth= or access_token= |
Hello guys.
How do I get DEFAULT_TOKEN configuration ?
I was using Firebase token generator php but it not working.
Can you help me ?
Thank a lot
The text was updated successfully, but these errors were encountered: