You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow-up to #28362, which has been closed.
I have actually set up an IDP (Identity Provider) and am able to authenticate, but what I want to do is after getting claims from the IDP, make a call to the app's API and get more app specific claims to merge with those from the IDP. This approach is described in a Pluralsight course by Kevin Dockx https://app.pluralsight.com/library/courses/dealing-credentials-when-securing-aspdotnet-core-3-application/table-of-contents. It uses Microsoft.AspNetCore.Authentication.OpenIdConnect, but the client is not Blazor. Do you know how I might implement this approach with a Blazor client?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
This is a follow-up to #28362, which has been closed.
I have actually set up an IDP (Identity Provider) and am able to authenticate, but what I want to do is after getting claims from the IDP, make a call to the app's API and get more app specific claims to merge with those from the IDP. This approach is described in a Pluralsight course by Kevin Dockx https://app.pluralsight.com/library/courses/dealing-credentials-when-securing-aspdotnet-core-3-application/table-of-contents. It uses Microsoft.AspNetCore.Authentication.OpenIdConnect, but the client is not Blazor. Do you know how I might implement this approach with a Blazor client?
Thanks,
Patrick
Beta Was this translation helpful? Give feedback.
All reactions