You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The basic DBSC spec describes both GET and POST requests to /securesession/refresh, the high level overview only uses GET with headers, but the refresh procedure is showing POST for the scenario where the server chooses to end the session. Is one of these outdated, or otherwise, how would an RP hint to the client which type of request to make?
The text was updated successfully, but these errors were encountered:
It seems the chart in high level overview is outdated. By design the registration and refresh procedure are very similar, so they should both use POST.
The basic DBSC spec describes both
GET
andPOST
requests to/securesession/refresh
, the high level overview only usesGET
with headers, but the refresh procedure is showingPOST
for the scenario where the server chooses to end the session. Is one of these outdated, or otherwise, how would an RP hint to the client which type of request to make?The text was updated successfully, but these errors were encountered: