What does this hospital mean with the following OAuth requirements? -
we've got hospital customer wants have app developed. app make use of various ways of validation, of oauth2 one. have list of requirements, of 1 kind of puzzles me:
for every user session, app needs generate unpredictable "state parameter". app needs validate "state value" every request sent redirect url; "state" needs recorded authorization requests; , "state value" has validated access token receives.
although don't mention guess talks oauth. i've got experience oauth2. know access tokens , refresh tokens are. story above head. kind of "state parameter"
, "state value"
talking about?
could shed light on story?
this state
parameter oauth 2.0 has defined in authorization request recommended parameter (https://tools.ietf.org/html/rfc6749#section-4.1.1) used protected against cross-site request forgery , correlate requests , responses in general:
state
recommended. opaque value used client maintain state between request , callback. authorization server includes value when redirecting user-agent client. parameter should used preventing cross-site request forgery described in section 10.12.
Comments
Post a Comment