Best practice to store web_client_id from firebase auth?
what is the best practice to store the web_client_id
that we get from firebase
in android?
is it in the string.xml
?
android
add a comment |
what is the best practice to store the web_client_id
that we get from firebase
in android?
is it in the string.xml
?
android
add a comment |
what is the best practice to store the web_client_id
that we get from firebase
in android?
is it in the string.xml
?
android
what is the best practice to store the web_client_id
that we get from firebase
in android?
is it in the string.xml
?
android
android
edited Nov 12 '18 at 8:14
Jayson Minard
37.8k15107170
37.8k15107170
asked Nov 12 '18 at 3:44
kazuyahiko
17611
17611
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There are several how you can do it. First of all, you can store such things in SharedPreferences (it's convenient to use SharedPreferences in key-value scenarios) - https://developer.android.com/reference/android/content/SharedPreferences
Second way - save it in memory. You also can combine these methods (for example, read a value from a memory, but update it in SharedPreferences).
If you need it, you can encrypt a value before saving (via a key in Keystore system).
nice, i'll give it a try. thanks.
– kazuyahiko
Nov 12 '18 at 8:11
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255696%2fbest-practice-to-store-web-client-id-from-firebase-auth%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are several how you can do it. First of all, you can store such things in SharedPreferences (it's convenient to use SharedPreferences in key-value scenarios) - https://developer.android.com/reference/android/content/SharedPreferences
Second way - save it in memory. You also can combine these methods (for example, read a value from a memory, but update it in SharedPreferences).
If you need it, you can encrypt a value before saving (via a key in Keystore system).
nice, i'll give it a try. thanks.
– kazuyahiko
Nov 12 '18 at 8:11
add a comment |
There are several how you can do it. First of all, you can store such things in SharedPreferences (it's convenient to use SharedPreferences in key-value scenarios) - https://developer.android.com/reference/android/content/SharedPreferences
Second way - save it in memory. You also can combine these methods (for example, read a value from a memory, but update it in SharedPreferences).
If you need it, you can encrypt a value before saving (via a key in Keystore system).
nice, i'll give it a try. thanks.
– kazuyahiko
Nov 12 '18 at 8:11
add a comment |
There are several how you can do it. First of all, you can store such things in SharedPreferences (it's convenient to use SharedPreferences in key-value scenarios) - https://developer.android.com/reference/android/content/SharedPreferences
Second way - save it in memory. You also can combine these methods (for example, read a value from a memory, but update it in SharedPreferences).
If you need it, you can encrypt a value before saving (via a key in Keystore system).
There are several how you can do it. First of all, you can store such things in SharedPreferences (it's convenient to use SharedPreferences in key-value scenarios) - https://developer.android.com/reference/android/content/SharedPreferences
Second way - save it in memory. You also can combine these methods (for example, read a value from a memory, but update it in SharedPreferences).
If you need it, you can encrypt a value before saving (via a key in Keystore system).
answered Nov 12 '18 at 5:07
Alex Shevelev
19718
19718
nice, i'll give it a try. thanks.
– kazuyahiko
Nov 12 '18 at 8:11
add a comment |
nice, i'll give it a try. thanks.
– kazuyahiko
Nov 12 '18 at 8:11
nice, i'll give it a try. thanks.
– kazuyahiko
Nov 12 '18 at 8:11
nice, i'll give it a try. thanks.
– kazuyahiko
Nov 12 '18 at 8:11
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53255696%2fbest-practice-to-store-web-client-id-from-firebase-auth%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown