Complex API + Page Permission Standards
I've been working on a project management system for quite sometime, and I'm constantly struggling with the right approach for permissions.
An example of where I struggle would be the following.
Assume I have customers and projects, and I want to make sure that only customer can see their own projects.
Currently I have to manually check each call to the projects controller to find out who the customer is, and make sure to only return their own projects.
I'm looking for proven permission designs that can handle complex hierarchy's.
I'm aware their is no "Right" answer, but I'm looking for suggestions.
api
add a comment |
I've been working on a project management system for quite sometime, and I'm constantly struggling with the right approach for permissions.
An example of where I struggle would be the following.
Assume I have customers and projects, and I want to make sure that only customer can see their own projects.
Currently I have to manually check each call to the projects controller to find out who the customer is, and make sure to only return their own projects.
I'm looking for proven permission designs that can handle complex hierarchy's.
I'm aware their is no "Right" answer, but I'm looking for suggestions.
api
add a comment |
I've been working on a project management system for quite sometime, and I'm constantly struggling with the right approach for permissions.
An example of where I struggle would be the following.
Assume I have customers and projects, and I want to make sure that only customer can see their own projects.
Currently I have to manually check each call to the projects controller to find out who the customer is, and make sure to only return their own projects.
I'm looking for proven permission designs that can handle complex hierarchy's.
I'm aware their is no "Right" answer, but I'm looking for suggestions.
api
I've been working on a project management system for quite sometime, and I'm constantly struggling with the right approach for permissions.
An example of where I struggle would be the following.
Assume I have customers and projects, and I want to make sure that only customer can see their own projects.
Currently I have to manually check each call to the projects controller to find out who the customer is, and make sure to only return their own projects.
I'm looking for proven permission designs that can handle complex hierarchy's.
I'm aware their is no "Right" answer, but I'm looking for suggestions.
api
api
asked Nov 13 '18 at 20:24
Tom CrosmanTom Crosman
113
113
add a comment |
add a comment |
0
active
oldest
votes
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%2f53288939%2fcomplex-api-page-permission-standards%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f53288939%2fcomplex-api-page-permission-standards%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