In OAuth 2.0, what are the responisibilities of a pure Resource server? -
we building "pure" resource server. "pure" mean none of our data user specific, , going called other programs no user interaction (ie cron job), , 1 user no public access. of tutorials on oauth 2.0 light on details regarding client credentials scenario, let alone 1 this.
for example of "pure" resource server can think of rest webservice controlls lights (on or off) in office building.
so, in oauth 2.0 responsibilities of such resource server?
from understanding must:
- check presence of bearer token.
- if token present validate token
- validating requires
- either requesting authorization server behind scenes validate it, or if using jwt :
- unpacking token
- (if present) checking signature/mac matches
- (if present) resource listed in audience
- (if present) checking token has not expired
- allowing call call if token valid, otherwise respond 403 , message
so, have 3 questions.
- is above correct?
- is there point in returning 302 redirect when know clients not browsers?
Comments
Post a Comment