Firebase Cloud Functions - Evaluate if user may be registered
up vote
0
down vote
favorite
Let's say I have a collection named people
, and each document of has a property name phone_number
.
Of course, I could allow a user to register, and if his phone number exists, I may consider him validated. But if the user doesn't have a phone number in any of the documents I mentioned before, I wouldn't want to let him register from the start.
How can I tell Firebase to allow users to register only if their phone numbers exists in the documents? In a different backend (such as nest) I would create a pipe that simply checks if the given phone number in the request exists.
firebase firebase-authentication google-cloud-functions
add a comment |
up vote
0
down vote
favorite
Let's say I have a collection named people
, and each document of has a property name phone_number
.
Of course, I could allow a user to register, and if his phone number exists, I may consider him validated. But if the user doesn't have a phone number in any of the documents I mentioned before, I wouldn't want to let him register from the start.
How can I tell Firebase to allow users to register only if their phone numbers exists in the documents? In a different backend (such as nest) I would create a pipe that simply checks if the given phone number in the request exists.
firebase firebase-authentication google-cloud-functions
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Let's say I have a collection named people
, and each document of has a property name phone_number
.
Of course, I could allow a user to register, and if his phone number exists, I may consider him validated. But if the user doesn't have a phone number in any of the documents I mentioned before, I wouldn't want to let him register from the start.
How can I tell Firebase to allow users to register only if their phone numbers exists in the documents? In a different backend (such as nest) I would create a pipe that simply checks if the given phone number in the request exists.
firebase firebase-authentication google-cloud-functions
Let's say I have a collection named people
, and each document of has a property name phone_number
.
Of course, I could allow a user to register, and if his phone number exists, I may consider him validated. But if the user doesn't have a phone number in any of the documents I mentioned before, I wouldn't want to let him register from the start.
How can I tell Firebase to allow users to register only if their phone numbers exists in the documents? In a different backend (such as nest) I would create a pipe that simply checks if the given phone number in the request exists.
firebase firebase-authentication google-cloud-functions
firebase firebase-authentication google-cloud-functions
asked Nov 10 at 22:45
Eliya Cohen
1,8801635
1,8801635
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
If I understand correctly your requirement, you should just check if there is a people doc with this phone_number in your collection, with a query through the Admin SDK.
So if I make the assumption you are going to use an HTTPS Cloud Function, something along the following lines should do the trick. It should be easy to adapt it to other Cloud Function triggers.
exports.registerUser = functions.https.onRequest((req, res) =>
const phone_number = req.body.phone_number;
const peopleCollecRef = admin.firestore().collection('people');
peopleCollecRef
.where('phone_number', '==', phone_number)
.get()
.then(querySnapshot =>
if (querySnapshot.size === 1)
return admin.auth().createUser(
email: req.body.email,
emailVerified: false,
phoneNumber: phone_number,
password: '....'
);
else
throw new Error('No user (or more than one user) with corresponding phone number ');
)
.then(userRecord =>
res.send( result: 'user created with id: ' + userRecord.uid ); //Just an example
)
.catch(error =>
res.status(500).send(error);
);
);
You should also probably flag when a user has been registered in order to avoid the phone number is used another time by another user. I men depending on your data model there are probably several checks to be implemented inthe Cloud Function.
@Eliya Cohen Hello, did you have the opportunity to look at the proposed solution?
– Renaud Tarnec
Nov 14 at 12:22
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',
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%2f53244164%2ffirebase-cloud-functions-evaluate-if-user-may-be-registered%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
up vote
0
down vote
If I understand correctly your requirement, you should just check if there is a people doc with this phone_number in your collection, with a query through the Admin SDK.
So if I make the assumption you are going to use an HTTPS Cloud Function, something along the following lines should do the trick. It should be easy to adapt it to other Cloud Function triggers.
exports.registerUser = functions.https.onRequest((req, res) =>
const phone_number = req.body.phone_number;
const peopleCollecRef = admin.firestore().collection('people');
peopleCollecRef
.where('phone_number', '==', phone_number)
.get()
.then(querySnapshot =>
if (querySnapshot.size === 1)
return admin.auth().createUser(
email: req.body.email,
emailVerified: false,
phoneNumber: phone_number,
password: '....'
);
else
throw new Error('No user (or more than one user) with corresponding phone number ');
)
.then(userRecord =>
res.send( result: 'user created with id: ' + userRecord.uid ); //Just an example
)
.catch(error =>
res.status(500).send(error);
);
);
You should also probably flag when a user has been registered in order to avoid the phone number is used another time by another user. I men depending on your data model there are probably several checks to be implemented inthe Cloud Function.
@Eliya Cohen Hello, did you have the opportunity to look at the proposed solution?
– Renaud Tarnec
Nov 14 at 12:22
add a comment |
up vote
0
down vote
If I understand correctly your requirement, you should just check if there is a people doc with this phone_number in your collection, with a query through the Admin SDK.
So if I make the assumption you are going to use an HTTPS Cloud Function, something along the following lines should do the trick. It should be easy to adapt it to other Cloud Function triggers.
exports.registerUser = functions.https.onRequest((req, res) =>
const phone_number = req.body.phone_number;
const peopleCollecRef = admin.firestore().collection('people');
peopleCollecRef
.where('phone_number', '==', phone_number)
.get()
.then(querySnapshot =>
if (querySnapshot.size === 1)
return admin.auth().createUser(
email: req.body.email,
emailVerified: false,
phoneNumber: phone_number,
password: '....'
);
else
throw new Error('No user (or more than one user) with corresponding phone number ');
)
.then(userRecord =>
res.send( result: 'user created with id: ' + userRecord.uid ); //Just an example
)
.catch(error =>
res.status(500).send(error);
);
);
You should also probably flag when a user has been registered in order to avoid the phone number is used another time by another user. I men depending on your data model there are probably several checks to be implemented inthe Cloud Function.
@Eliya Cohen Hello, did you have the opportunity to look at the proposed solution?
– Renaud Tarnec
Nov 14 at 12:22
add a comment |
up vote
0
down vote
up vote
0
down vote
If I understand correctly your requirement, you should just check if there is a people doc with this phone_number in your collection, with a query through the Admin SDK.
So if I make the assumption you are going to use an HTTPS Cloud Function, something along the following lines should do the trick. It should be easy to adapt it to other Cloud Function triggers.
exports.registerUser = functions.https.onRequest((req, res) =>
const phone_number = req.body.phone_number;
const peopleCollecRef = admin.firestore().collection('people');
peopleCollecRef
.where('phone_number', '==', phone_number)
.get()
.then(querySnapshot =>
if (querySnapshot.size === 1)
return admin.auth().createUser(
email: req.body.email,
emailVerified: false,
phoneNumber: phone_number,
password: '....'
);
else
throw new Error('No user (or more than one user) with corresponding phone number ');
)
.then(userRecord =>
res.send( result: 'user created with id: ' + userRecord.uid ); //Just an example
)
.catch(error =>
res.status(500).send(error);
);
);
You should also probably flag when a user has been registered in order to avoid the phone number is used another time by another user. I men depending on your data model there are probably several checks to be implemented inthe Cloud Function.
If I understand correctly your requirement, you should just check if there is a people doc with this phone_number in your collection, with a query through the Admin SDK.
So if I make the assumption you are going to use an HTTPS Cloud Function, something along the following lines should do the trick. It should be easy to adapt it to other Cloud Function triggers.
exports.registerUser = functions.https.onRequest((req, res) =>
const phone_number = req.body.phone_number;
const peopleCollecRef = admin.firestore().collection('people');
peopleCollecRef
.where('phone_number', '==', phone_number)
.get()
.then(querySnapshot =>
if (querySnapshot.size === 1)
return admin.auth().createUser(
email: req.body.email,
emailVerified: false,
phoneNumber: phone_number,
password: '....'
);
else
throw new Error('No user (or more than one user) with corresponding phone number ');
)
.then(userRecord =>
res.send( result: 'user created with id: ' + userRecord.uid ); //Just an example
)
.catch(error =>
res.status(500).send(error);
);
);
You should also probably flag when a user has been registered in order to avoid the phone number is used another time by another user. I men depending on your data model there are probably several checks to be implemented inthe Cloud Function.
edited Nov 11 at 8:35
answered Nov 11 at 8:28
Renaud Tarnec
9,97421431
9,97421431
@Eliya Cohen Hello, did you have the opportunity to look at the proposed solution?
– Renaud Tarnec
Nov 14 at 12:22
add a comment |
@Eliya Cohen Hello, did you have the opportunity to look at the proposed solution?
– Renaud Tarnec
Nov 14 at 12:22
@Eliya Cohen Hello, did you have the opportunity to look at the proposed solution?
– Renaud Tarnec
Nov 14 at 12:22
@Eliya Cohen Hello, did you have the opportunity to look at the proposed solution?
– Renaud Tarnec
Nov 14 at 12:22
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%2f53244164%2ffirebase-cloud-functions-evaluate-if-user-may-be-registered%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