-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post-interaction static page #58
Comments
|
I can almost see how this would be useful, but I think we should have a concrete use case before adding a new method. |
|
Alternate proposal: Add a field to the |
|
No concrete use cases have been brought forward, closing. Could be added as extension to interaction methods if desired by community. |
§2.5.3 Receive a Callback After Interaction: Editor's note:
There has been some call for a post-interaction redirect that is not tied to the underlying security model - specifically, sending the user over to a client-hosted page with client-specific instructions on how to continue. This would be something hosted externally to the client instance, so the client instance would never see this incoming call. We could accomplish that using this "callback" post-redirect mechanism but with "method": "static" or "nonce": false or some other signal to indicate that the client won't see the incoming request.
The text was updated successfully, but these errors were encountered: