Rest API Scope Mapping with OAuth
up vote
0
down vote
favorite
Let me explain my doubt with an example:
Following Rest API's are created for an enterprise.
1. /customer
2. /billpay
3. /employee
Now one of the requirement is to implement the scopets. For eg : Only an employee could should be able to access the /employee api.
We see that that there is a scope in OAuth2.0 that could be used but not exactly how it fits.
Is it that we should create a scope named "emp" and assign the different urls that comes under the scope "emp". Where is the logic of mapping the scope of urls implemented ?. Is it in the OAuth specification and implemented by OAuth Server ? Or it should be seperately implemented
in the rest service or in some common gateway?
Can anyone please explain?
rest oauth-2.0
asked Nov 20 at 4:10
TechiePro
84
add a comment |
up vote
0
down vote
favorite
Let me explain my doubt with an example:
Following Rest API's are created for an enterprise.
1. /customer
2. /billpay
3. /employee
Now one of the requirement is to implement the scopets. For eg : Only an employee could should be able to access the /employee api.
We see that that there is a scope in OAuth2.0 that could be used but not exactly how it fits.
Is it that we should create a scope named "emp" and assign the different urls that comes under the scope "emp". Where is the logic of mapping the scope of urls implemented ?. Is it in the OAuth specification and implemented by OAuth Server ? Or it should be seperately implemented
in the rest service or in some common gateway?
Can anyone please explain?
rest oauth-2.0
asked Nov 20 at 4:10
TechiePro
84
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Let me explain my doubt with an example:
Following Rest API's are created for an enterprise.
1. /customer
2. /billpay
3. /employee
Now one of the requirement is to implement the scopets. For eg : Only an employee could should be able to access the /employee api.
We see that that there is a scope in OAuth2.0 that could be used but not exactly how it fits.
Is it that we should create a scope named "emp" and assign the different urls that comes under the scope "emp". Where is the logic of mapping the scope of urls implemented ?. Is it in the OAuth specification and implemented by OAuth Server ? Or it should be seperately implemented
in the rest service or in some common gateway?
Can anyone please explain?
rest oauth-2.0
asked Nov 20 at 4:10
TechiePro
84
Let me explain my doubt with an example:
Following Rest API's are created for an enterprise.
1. /customer
2. /billpay
3. /employee
Now one of the requirement is to implement the scopets. For eg : Only an employee could should be able to access the /employee api.
We see that that there is a scope in OAuth2.0 that could be used but not exactly how it fits.
Is it that we should create a scope named "emp" and assign the different urls that comes under the scope "emp". Where is the logic of mapping the scope of urls implemented ?. Is it in the OAuth specification and implemented by OAuth Server ? Or it should be seperately implemented
in the rest service or in some common gateway?
Can anyone please explain?
rest oauth-2.0
rest oauth-2.0
asked Nov 20 at 4:10
TechiePro
84
asked Nov 20 at 4:10
TechiePro
84
asked Nov 20 at 4:10
TechiePro
84
asked Nov 20 at 4:10
TechiePro
84
asked Nov 20 at 4:10
TechiePro
84
84
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
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.
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%2f53386099%2frest-api-scope-mapping-with-oauth%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
