-
Notifications
You must be signed in to change notification settings - Fork 19
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
Move videos to Youtube #224
Comments
Videos include some outdated information, probably we should hint that in README
Actually, Authorization Agent is intended to be a server-side service. Generating access grants from access consents. Subscribing to agent registrations on behalf of the grantee, all that makes more sense to run as server-side service. |
Discussed in panel meeting of 2022-01-25: videos's could be moved to YouTube, where bubble comments can be used to annotate specific moments of divergence from newer drafts. Serverside AA is also totally clear now, thx! |
I believe the video intro's to the interop spec describe a "security by obscurity" mechanism for application registration discovery using hashed client IDs. However, in the current draft, I can no longer find this idea, and discovery seems to happen via a header from the Authorization Agent.
My first question is therefore to clarify that this is indeed a change, and maybe indicate that the video intro's do no longer contain all the latest information.
Secondly, and more importantly i.m.o., this seems to entail that the Authorization Agent needs some kind of back-end for this mechanism to work. Up till now, I had always seen that agent as a front-end only application. Is this not the case?
The text was updated successfully, but these errors were encountered: