Repository navigation
[12.0 P1] Document passwordless account creation in the Blazor passkeys article - #37773
aspnetcore-docs-bot[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@rolandVi, this draft documents your source change in dotnet/aspnetcore#68648. Please review it for technical accuracy and confirm that the user impact and recommended guidance match the implementation. |
|
@BillWagner @gewarren ... We have no 12.0 moniker established for the repo yet. Do you want to add it now? |
|
@guardrex @tdykstra, this is a test PR from the aspnetcore workflow. The idea is to automatically process the merged PRs, and if AI thinks there is a good reason to document this (aka new feature, or new behavior, or breaking change etc), then it posts a PR here. Since this is a draft, you can ignore this. One PRs open, they are in ready-for-review state. Does this process work for you? This will help us move faster with the docs and not forget to document anything. Let me know if you have propositions, or suggestions. |
|
All good, @DeagleGross, 👍 ... but note that Tom and Wade no longer work on this repo. I'm the only dedicated docs person left here, and it's unclear at this time if I'll still be around after December. If you need to interact with docs MS FTEs/managers about the repo, then @BillWagner and/or @gewarren are the contacts. |
|
Thanks Luke! btw aspnetcore onboarded to net12: dotnet/aspnetcore#69553, so i think 12.0 moniker should be prepared |
Done! |
|
Thanks, @gewarren. @DeagleGross ... I changed the title to indicate 12.0 P1, which will probably be scheduled for February, 2027. PRs for the P1 release can accumulate here for the reference articles. It's still unknown if What's New content will move to Copilot generation. I think it would be a good idea to set that up. We doc authors are rapidly becoming real dinosaurs around here 🦖😄. |
|
@gewarren ... @aspnetcore-docs-bot[bot] triggered the CLA ☝️. |
|
@aspnetcore-docs-bot[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by .NET Foundation and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and .NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. |
|
Fixing CLA on docs-bot: dotnet/.github#28 |
Source: dotnet/aspnetcore#68648
Documentation confidence: 80
/PasskeyRegistrationOptionsendpoint.Summary: Extended
security/authentication/passkeys/blazorwith 12.0-scoped sections for the registration endpoint, the Register page update, and creating an account with a passkey.Modified files:
aspnetcore/security/authentication/passkeys/blazor.mdInternal previews
Build report