-
Notifications
You must be signed in to change notification settings - Fork 305
Extend 403 template to request access #992
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
Comments
hard to have any input without seeing the full processes and progress you have made. Everyone requires from birth until 17 years of age some form of Web Identity. Parents control until they take ownership. Pass 'Phrases' are used in crypto hard wallets and other items trying to be made as safe as possible. Not sure if this helps of is even relevant. All the best |
Can I suggest that when you get a 403 the client opens a websocket to the resource, and it does a reload if the acl is updated? I envisage a few ways to make this happen. At the moment it will be out of band. |
Next step in the interaction:
Offer an input (button or whatever) to the user to make a request to access the resource.
There can be a number of ways to that.. config setting that shows the request form on all 403s and sends a notification to an (dedicated?) inbox, and/or if the resource has a dedicated inbox....
I said template in the title of this issue, but it'll act more like its own application (so that the server is not expected to process it like an HTML form) that sends a notification.
The text was updated successfully, but these errors were encountered: