search

ChristianWeyer / myProducts-End-to-End

A modern business application with HTML5, JavaScript & .NET: sample secure master-detail application with AngularJS, ASP.NET Web API, SignalR. Uses Cordova/Phonegap and node-webkit (nw.js).
35 stars 10 forks source link

OpenId Connect / identityServer v3 #13

Closed galenp closed 8 years ago

galenp commented 10 years ago

Hi Christian, How are you going with the OIDC branch? Is this functioning for the most part?

galenp commented 10 years ago

I've been delving deeper into this implementation as this is very similar to our own desired way of setting up our system and it's connection with IdSvr3.

What I'm currently challenged with and it seems this part is still not covered in this branch is having the PersonlizationController correctly pickup the full claims user.

My understanding of what should happen is that when the angular end-user does the GET to /personlization a new OpenId request is sent to IdSvr with the profile scope. This should return back the full profile for the user and you would then build your Personlization DTO.

Is that correct?

Or is there some other plumbing that occurs in the Oauth2 authentication process which handles this and sticks the claims into the ClaimsPrinciple. (I believe this is how the original branch worked).

A penny for your thoughts Christian.

ChristianWeyer commented 8 years ago

Sorry - this issue never popped up in my notification list :(