Firebase Rule - Match document to user via email address
I'm trying to get a simple rule to work: If a document from my records
collection contains an email (fatherEmail || motherEmail
) that matches the email of the user logging in, allow that doc to be read. Not working - Missing or insufficient permissions
.
Here are my rules:
Per Firebase tech support the recommended way to retrieve the auth'd user's email address:
function getUserEmail(){
return request.auth.token.email;
}
Here’s the Stackblitz:
https://stackblitz.com/edit/login-and-match-record-mvce?file=src%2Fapp%2Fauth.service.ts
Login using a verified email:
User: devcore2911@gmail.com
Pass: foobar
If you look at the console, you'll see the error I mentioned above.
My records
collection contains one document that contains devcore2911@gmail.com
as the value for thefatherEmail
property so that doc should pull up:
firebase google-cloud-firestore firebase-security-rules
add a comment |
I'm trying to get a simple rule to work: If a document from my records
collection contains an email (fatherEmail || motherEmail
) that matches the email of the user logging in, allow that doc to be read. Not working - Missing or insufficient permissions
.
Here are my rules:
Per Firebase tech support the recommended way to retrieve the auth'd user's email address:
function getUserEmail(){
return request.auth.token.email;
}
Here’s the Stackblitz:
https://stackblitz.com/edit/login-and-match-record-mvce?file=src%2Fapp%2Fauth.service.ts
Login using a verified email:
User: devcore2911@gmail.com
Pass: foobar
If you look at the console, you'll see the error I mentioned above.
My records
collection contains one document that contains devcore2911@gmail.com
as the value for thefatherEmail
property so that doc should pull up:
firebase google-cloud-firestore firebase-security-rules
add a comment |
I'm trying to get a simple rule to work: If a document from my records
collection contains an email (fatherEmail || motherEmail
) that matches the email of the user logging in, allow that doc to be read. Not working - Missing or insufficient permissions
.
Here are my rules:
Per Firebase tech support the recommended way to retrieve the auth'd user's email address:
function getUserEmail(){
return request.auth.token.email;
}
Here’s the Stackblitz:
https://stackblitz.com/edit/login-and-match-record-mvce?file=src%2Fapp%2Fauth.service.ts
Login using a verified email:
User: devcore2911@gmail.com
Pass: foobar
If you look at the console, you'll see the error I mentioned above.
My records
collection contains one document that contains devcore2911@gmail.com
as the value for thefatherEmail
property so that doc should pull up:
firebase google-cloud-firestore firebase-security-rules
I'm trying to get a simple rule to work: If a document from my records
collection contains an email (fatherEmail || motherEmail
) that matches the email of the user logging in, allow that doc to be read. Not working - Missing or insufficient permissions
.
Here are my rules:
Per Firebase tech support the recommended way to retrieve the auth'd user's email address:
function getUserEmail(){
return request.auth.token.email;
}
Here’s the Stackblitz:
https://stackblitz.com/edit/login-and-match-record-mvce?file=src%2Fapp%2Fauth.service.ts
Login using a verified email:
User: devcore2911@gmail.com
Pass: foobar
If you look at the console, you'll see the error I mentioned above.
My records
collection contains one document that contains devcore2911@gmail.com
as the value for thefatherEmail
property so that doc should pull up:
firebase google-cloud-firestore firebase-security-rules
firebase google-cloud-firestore firebase-security-rules
edited Nov 12 '18 at 19:45
Doug Stevenson
70.9k881101
70.9k881101
asked Nov 12 '18 at 19:28
Jeremiah2911
231514
231514
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The solution: I must perform a query to filter out the docs that match the user's email.
See this stackblitz: https://stackblitz.com/edit/login-and-match-record-mvce?file=src%2Fapp%2Frecord-list%2Frecord-list.component.ts
Here's the code that solved the issue. Note the use of combineLatest
as Firebase queries do not support the ||
operator.
const matchFatherEmail = this.afs.collection("records", ref => ref.where("fatherEmail","==", this.authService.user.email));
const matchMotherEmail = this.afs.collection("records", ref => ref.where("motherEmail","==", this.authService.user.email));
this.records$ = combineLatest(matchFatherEmail.valueChanges(), matchMotherEmail.valueChanges())
.pipe(switchMap(docs => {
const [docsFatherEmail, docsMotherEmail] = docs;
const combined = docsFatherEmail.concat(docsMotherEmail);
return of(combined);
}))
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%2f53268839%2ffirebase-rule-match-document-to-user-via-email-address%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
The solution: I must perform a query to filter out the docs that match the user's email.
See this stackblitz: https://stackblitz.com/edit/login-and-match-record-mvce?file=src%2Fapp%2Frecord-list%2Frecord-list.component.ts
Here's the code that solved the issue. Note the use of combineLatest
as Firebase queries do not support the ||
operator.
const matchFatherEmail = this.afs.collection("records", ref => ref.where("fatherEmail","==", this.authService.user.email));
const matchMotherEmail = this.afs.collection("records", ref => ref.where("motherEmail","==", this.authService.user.email));
this.records$ = combineLatest(matchFatherEmail.valueChanges(), matchMotherEmail.valueChanges())
.pipe(switchMap(docs => {
const [docsFatherEmail, docsMotherEmail] = docs;
const combined = docsFatherEmail.concat(docsMotherEmail);
return of(combined);
}))
add a comment |
The solution: I must perform a query to filter out the docs that match the user's email.
See this stackblitz: https://stackblitz.com/edit/login-and-match-record-mvce?file=src%2Fapp%2Frecord-list%2Frecord-list.component.ts
Here's the code that solved the issue. Note the use of combineLatest
as Firebase queries do not support the ||
operator.
const matchFatherEmail = this.afs.collection("records", ref => ref.where("fatherEmail","==", this.authService.user.email));
const matchMotherEmail = this.afs.collection("records", ref => ref.where("motherEmail","==", this.authService.user.email));
this.records$ = combineLatest(matchFatherEmail.valueChanges(), matchMotherEmail.valueChanges())
.pipe(switchMap(docs => {
const [docsFatherEmail, docsMotherEmail] = docs;
const combined = docsFatherEmail.concat(docsMotherEmail);
return of(combined);
}))
add a comment |
The solution: I must perform a query to filter out the docs that match the user's email.
See this stackblitz: https://stackblitz.com/edit/login-and-match-record-mvce?file=src%2Fapp%2Frecord-list%2Frecord-list.component.ts
Here's the code that solved the issue. Note the use of combineLatest
as Firebase queries do not support the ||
operator.
const matchFatherEmail = this.afs.collection("records", ref => ref.where("fatherEmail","==", this.authService.user.email));
const matchMotherEmail = this.afs.collection("records", ref => ref.where("motherEmail","==", this.authService.user.email));
this.records$ = combineLatest(matchFatherEmail.valueChanges(), matchMotherEmail.valueChanges())
.pipe(switchMap(docs => {
const [docsFatherEmail, docsMotherEmail] = docs;
const combined = docsFatherEmail.concat(docsMotherEmail);
return of(combined);
}))
The solution: I must perform a query to filter out the docs that match the user's email.
See this stackblitz: https://stackblitz.com/edit/login-and-match-record-mvce?file=src%2Fapp%2Frecord-list%2Frecord-list.component.ts
Here's the code that solved the issue. Note the use of combineLatest
as Firebase queries do not support the ||
operator.
const matchFatherEmail = this.afs.collection("records", ref => ref.where("fatherEmail","==", this.authService.user.email));
const matchMotherEmail = this.afs.collection("records", ref => ref.where("motherEmail","==", this.authService.user.email));
this.records$ = combineLatest(matchFatherEmail.valueChanges(), matchMotherEmail.valueChanges())
.pipe(switchMap(docs => {
const [docsFatherEmail, docsMotherEmail] = docs;
const combined = docsFatherEmail.concat(docsMotherEmail);
return of(combined);
}))
answered Nov 20 '18 at 22:39
Jeremiah2911
231514
231514
add a comment |
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%2f53268839%2ffirebase-rule-match-document-to-user-via-email-address%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