How to implement row level security in ASP.NET boilerplate?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I started using ASP.NET Boilerplate a month back, so this is a beginner-level question. I feel it's a great framework — thanks a lot for creating and sharing this.



I was developing a multi-tenant application and now I want to filter rows based on tenant. What is the correct way of doing it in ASP.NET Boilerplate? I was thinking of passing TenantId with every DB call or creating a request context, which would have all details, and passing that along to the method call. And then, in the method, check if that particular row's TenantId matches with what we are passing. If not then discard, else proceed. With a few tweaks here and there, I may achieve what I want, but I want to know what is the correct way of doing it in ASP.NET Boilerplate.



Second, any out-of-the-box example of integrating Row Level Security feature of SQL Server in ASP.NET Boilerplate?



Thanks a lot.










share|improve this question

























  • Welcome. Could you just paste the code along with the description?

    – Bruno Berisso
    Nov 23 '18 at 18:33


















0















I started using ASP.NET Boilerplate a month back, so this is a beginner-level question. I feel it's a great framework — thanks a lot for creating and sharing this.



I was developing a multi-tenant application and now I want to filter rows based on tenant. What is the correct way of doing it in ASP.NET Boilerplate? I was thinking of passing TenantId with every DB call or creating a request context, which would have all details, and passing that along to the method call. And then, in the method, check if that particular row's TenantId matches with what we are passing. If not then discard, else proceed. With a few tweaks here and there, I may achieve what I want, but I want to know what is the correct way of doing it in ASP.NET Boilerplate.



Second, any out-of-the-box example of integrating Row Level Security feature of SQL Server in ASP.NET Boilerplate?



Thanks a lot.










share|improve this question

























  • Welcome. Could you just paste the code along with the description?

    – Bruno Berisso
    Nov 23 '18 at 18:33














0












0








0








I started using ASP.NET Boilerplate a month back, so this is a beginner-level question. I feel it's a great framework — thanks a lot for creating and sharing this.



I was developing a multi-tenant application and now I want to filter rows based on tenant. What is the correct way of doing it in ASP.NET Boilerplate? I was thinking of passing TenantId with every DB call or creating a request context, which would have all details, and passing that along to the method call. And then, in the method, check if that particular row's TenantId matches with what we are passing. If not then discard, else proceed. With a few tweaks here and there, I may achieve what I want, but I want to know what is the correct way of doing it in ASP.NET Boilerplate.



Second, any out-of-the-box example of integrating Row Level Security feature of SQL Server in ASP.NET Boilerplate?



Thanks a lot.










share|improve this question
















I started using ASP.NET Boilerplate a month back, so this is a beginner-level question. I feel it's a great framework — thanks a lot for creating and sharing this.



I was developing a multi-tenant application and now I want to filter rows based on tenant. What is the correct way of doing it in ASP.NET Boilerplate? I was thinking of passing TenantId with every DB call or creating a request context, which would have all details, and passing that along to the method call. And then, in the method, check if that particular row's TenantId matches with what we are passing. If not then discard, else proceed. With a few tweaks here and there, I may achieve what I want, but I want to know what is the correct way of doing it in ASP.NET Boilerplate.



Second, any out-of-the-box example of integrating Row Level Security feature of SQL Server in ASP.NET Boilerplate?



Thanks a lot.







asp.net sql-server multi-tenant aspnetboilerplate row-level-security






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '18 at 23:37









aaron

9,44431237




9,44431237










asked Nov 23 '18 at 18:13









ZainudeenZainudeen

32




32













  • Welcome. Could you just paste the code along with the description?

    – Bruno Berisso
    Nov 23 '18 at 18:33



















  • Welcome. Could you just paste the code along with the description?

    – Bruno Berisso
    Nov 23 '18 at 18:33

















Welcome. Could you just paste the code along with the description?

– Bruno Berisso
Nov 23 '18 at 18:33





Welcome. Could you just paste the code along with the description?

– Bruno Berisso
Nov 23 '18 at 18:33












1 Answer
1






active

oldest

votes


















0















I was developing a multi-tenant application and now I want to filter rows based on tenant. What is the correct way of doing it in ASP.NET Boilerplate? I was thinking of passing TenantId with every DB call or creating a request context, which would have all details, and passing that along to the method call. And then, in the method, check if that particular row's TenantId matches with what we are passing. If not then discard, else proceed.




That's a built-in feature of ASP.NET Boilerplate, implemented via EF Core's Global Query Filters.



More info: https://aspnetboilerplate.com/Pages/Documents/Multi-Tenancy#data-filters




Second, any out-of-the-box example of integrating Row Level Security feature of SQL Server in ASP.NET Boilerplate?




No, all DB calls are made by the same trusted DB user determined by the connection string.



You might have misunderstood Row-Level Security.



You could pass a different connection string based on the application user, but that's simply application-level authorization — also built-in, implemented via Castle Windsor's Interceptors.



More info: https://aspnetboilerplate.com/Pages/Documents/Authorization






share|improve this answer
























  • aspnetboilerplate.com/Pages/Documents/… ideally explains the filter with TenantId and with IPermissionChecker (aspnetboilerplate.com/Pages/Documents/Authorization ) I can achieve what I want.Thanks a lot for sharing these details.

    – Zainudeen
    Nov 24 '18 at 14:58














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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53451324%2fhow-to-implement-row-level-security-in-asp-net-boilerplate%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









0















I was developing a multi-tenant application and now I want to filter rows based on tenant. What is the correct way of doing it in ASP.NET Boilerplate? I was thinking of passing TenantId with every DB call or creating a request context, which would have all details, and passing that along to the method call. And then, in the method, check if that particular row's TenantId matches with what we are passing. If not then discard, else proceed.




That's a built-in feature of ASP.NET Boilerplate, implemented via EF Core's Global Query Filters.



More info: https://aspnetboilerplate.com/Pages/Documents/Multi-Tenancy#data-filters




Second, any out-of-the-box example of integrating Row Level Security feature of SQL Server in ASP.NET Boilerplate?




No, all DB calls are made by the same trusted DB user determined by the connection string.



You might have misunderstood Row-Level Security.



You could pass a different connection string based on the application user, but that's simply application-level authorization — also built-in, implemented via Castle Windsor's Interceptors.



More info: https://aspnetboilerplate.com/Pages/Documents/Authorization






share|improve this answer
























  • aspnetboilerplate.com/Pages/Documents/… ideally explains the filter with TenantId and with IPermissionChecker (aspnetboilerplate.com/Pages/Documents/Authorization ) I can achieve what I want.Thanks a lot for sharing these details.

    – Zainudeen
    Nov 24 '18 at 14:58


















0















I was developing a multi-tenant application and now I want to filter rows based on tenant. What is the correct way of doing it in ASP.NET Boilerplate? I was thinking of passing TenantId with every DB call or creating a request context, which would have all details, and passing that along to the method call. And then, in the method, check if that particular row's TenantId matches with what we are passing. If not then discard, else proceed.




That's a built-in feature of ASP.NET Boilerplate, implemented via EF Core's Global Query Filters.



More info: https://aspnetboilerplate.com/Pages/Documents/Multi-Tenancy#data-filters




Second, any out-of-the-box example of integrating Row Level Security feature of SQL Server in ASP.NET Boilerplate?




No, all DB calls are made by the same trusted DB user determined by the connection string.



You might have misunderstood Row-Level Security.



You could pass a different connection string based on the application user, but that's simply application-level authorization — also built-in, implemented via Castle Windsor's Interceptors.



More info: https://aspnetboilerplate.com/Pages/Documents/Authorization






share|improve this answer
























  • aspnetboilerplate.com/Pages/Documents/… ideally explains the filter with TenantId and with IPermissionChecker (aspnetboilerplate.com/Pages/Documents/Authorization ) I can achieve what I want.Thanks a lot for sharing these details.

    – Zainudeen
    Nov 24 '18 at 14:58
















0












0








0








I was developing a multi-tenant application and now I want to filter rows based on tenant. What is the correct way of doing it in ASP.NET Boilerplate? I was thinking of passing TenantId with every DB call or creating a request context, which would have all details, and passing that along to the method call. And then, in the method, check if that particular row's TenantId matches with what we are passing. If not then discard, else proceed.




That's a built-in feature of ASP.NET Boilerplate, implemented via EF Core's Global Query Filters.



More info: https://aspnetboilerplate.com/Pages/Documents/Multi-Tenancy#data-filters




Second, any out-of-the-box example of integrating Row Level Security feature of SQL Server in ASP.NET Boilerplate?




No, all DB calls are made by the same trusted DB user determined by the connection string.



You might have misunderstood Row-Level Security.



You could pass a different connection string based on the application user, but that's simply application-level authorization — also built-in, implemented via Castle Windsor's Interceptors.



More info: https://aspnetboilerplate.com/Pages/Documents/Authorization






share|improve this answer














I was developing a multi-tenant application and now I want to filter rows based on tenant. What is the correct way of doing it in ASP.NET Boilerplate? I was thinking of passing TenantId with every DB call or creating a request context, which would have all details, and passing that along to the method call. And then, in the method, check if that particular row's TenantId matches with what we are passing. If not then discard, else proceed.




That's a built-in feature of ASP.NET Boilerplate, implemented via EF Core's Global Query Filters.



More info: https://aspnetboilerplate.com/Pages/Documents/Multi-Tenancy#data-filters




Second, any out-of-the-box example of integrating Row Level Security feature of SQL Server in ASP.NET Boilerplate?




No, all DB calls are made by the same trusted DB user determined by the connection string.



You might have misunderstood Row-Level Security.



You could pass a different connection string based on the application user, but that's simply application-level authorization — also built-in, implemented via Castle Windsor's Interceptors.



More info: https://aspnetboilerplate.com/Pages/Documents/Authorization







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 23 '18 at 23:51









aaronaaron

9,44431237




9,44431237













  • aspnetboilerplate.com/Pages/Documents/… ideally explains the filter with TenantId and with IPermissionChecker (aspnetboilerplate.com/Pages/Documents/Authorization ) I can achieve what I want.Thanks a lot for sharing these details.

    – Zainudeen
    Nov 24 '18 at 14:58





















  • aspnetboilerplate.com/Pages/Documents/… ideally explains the filter with TenantId and with IPermissionChecker (aspnetboilerplate.com/Pages/Documents/Authorization ) I can achieve what I want.Thanks a lot for sharing these details.

    – Zainudeen
    Nov 24 '18 at 14:58



















aspnetboilerplate.com/Pages/Documents/… ideally explains the filter with TenantId and with IPermissionChecker (aspnetboilerplate.com/Pages/Documents/Authorization ) I can achieve what I want.Thanks a lot for sharing these details.

– Zainudeen
Nov 24 '18 at 14:58







aspnetboilerplate.com/Pages/Documents/… ideally explains the filter with TenantId and with IPermissionChecker (aspnetboilerplate.com/Pages/Documents/Authorization ) I can achieve what I want.Thanks a lot for sharing these details.

– Zainudeen
Nov 24 '18 at 14:58






















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53451324%2fhow-to-implement-row-level-security-in-asp-net-boilerplate%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

RAC Tourist Trophy