Skip to content
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

.NET 8: MapIdentityApi<TUser>() #29363

Closed
Tracked by #28596
Rick-Anderson opened this issue May 26, 2023 · 4 comments · Fixed by #31010
Closed
Tracked by #28596

.NET 8: MapIdentityApi<TUser>() #29363

Rick-Anderson opened this issue May 26, 2023 · 4 comments · Fixed by #31010
Assignees
Labels
8.0 .NET 8 Blazor doc-enhancement Pri1 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@Rick-Anderson
Copy link
Contributor

Rick-Anderson commented May 26, 2023

See MapIdentityApi<TUser>()

Related: #30066

The main goal of the MapIdentityApi is to make it easy for developers to use ASP.NET Core Identity for authentication in JavaScript-based single page apps (SPA) or Blazor apps.

Since it's for Blazor app, assigning to @guardrex. If you don't want this, let me know.


Associated WorkItem - 159474

@danroth27
Copy link
Member

@guardrex @JeremyLikness Let's track the doc work for using Blazor with the new Identity endpoints separately. This issue should track generically documenting the Identity endpoints so they can be used from any client.

@guardrex
Copy link
Collaborator

I've opened a Blazor-specific issue, and I'll keep an 👁️ on this and the tokens issue.

#30394

@Rick-Anderson
Copy link
Contributor Author

@JeremyLikness can you provide a draft for this?

@JeremyLikness
Copy link
Member

Let me sync with @halter73 and make sure we're not duplicating effort. Is this a conceptual document about the API?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.0 .NET 8 Blazor doc-enhancement Pri1 seQUESTered Identifies that an issue has been imported into Quest.
Projects
Archived in project
Status: Done
Development

Successfully merging a pull request may close this issue.

6 participants