Closed BrainCrumbz closed 8 years ago
Why there are two projects (Mvc.Client and Mvc.Server), what are their roles/ functions in the context of OpenIdConnect authentication.
Basically:
Mvc.Client
is the OpenID Connect client application (a MVC app using app.UseOpenIdConnectAuthentication()
in this case).Mvc.Server
is both the resource server and the authorization server (a MVC app too). Note that you can of course separate the two roles.A simple and effective way to document that could be in a readme.md in that sub-directory.
Great idea. Would you like to submit a PR to fix that? :smile:
Thanks for your feedback.
Sorry, not everything looks totally clear yet.
Mvc.Client
web application offers to the user (or to this system we're looking at) ?
Mvc.Server
.
Just to make it clear, it would be nice to give to visitor a picture of what is the context of this sample, before one starts digging into code, so that if she's looking for a particular scenario or use case, she knows where to look at. And first of all, she knows if this example fits her needs.
Great idea. Would you like to submit a PR to fix that? :smile:
That was expected :smile: Happy to submit as soon as things are clear enough
What resources/ pages/ API endpoints does the Mvc.Client web application offers to the user (or to this system we're looking at) ?
HomeController
allows you to make an API query using the access token retrieved during the authorization process.
Is there a meaningful client-side code to be aware of? Or is logic all on server-side?
Nope, nothing interesting in the JS part, everything is handled server-side.
Being an authorization server, shouldn't it provide the API endpoints for requiring/ refreshing tokens? Why then it's an MVC app?
It does. MVC is just used to display the consent form (AuthorizationController
) and to offer a tiny token-protected API sample (ResourceController
)
Being a resource server, how does it offer resources to user? As an MVC app, with views, controllers, etc.?
Take a look at the resource controller. There's no views for the resource server part since it's just an API. The views are exclusively used for the consent pages.
Is there a meaningful client-side code to be aware of? Or is logic all on server-side?
Same answer as above.
Please have a look at PR #11
While looking at MVC sample and trying to have a better understanding of how to use those samples, it would be good to have a minimal explanation on why there are two projects (
Mvc.Client
andMvc.Server
), what are their roles/ functions in the context of OpenIdConnect authentication.They both provide a server application (although the former is dubbed client), they both have a
wwwroot
directory with client-side assets and/or scripts, so it is not immediately evident what are they for.A simple and effective way to document that could be in a readme.md in that sub-directory.
Thanks!