Skip to content

[UUF] Schema link is broken #11241

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.

Sign up for GitHub

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

Jump to bottom
Closed
gewarren opened this issue Apr 25, 2025 · 3 comments · Fixed by #11249
Closed

[UUF] Schema link is broken #11241

gewarren opened this issue Apr 25, 2025 · 3 comments · Fixed by #11249
Assignees
@gewarren
Labels
area-System.Security Issues related to security practices for .NET developers. 📌 seQUESTered Identifies that an issue has been imported into Quest. user-feedback

Comments

@gewarren
Copy link
Contributor

gewarren commented Apr 25, 2025 •
edited by sequestor bot
Loading

Type of issue

Missing information

Description

Schema link is broken.

Page URL

https://learn.microsoft.com/en-us/dotnet/api/system.security.claims.claimtypes.role?view=net-9.0

Content source URL

https://github.com/dotnet/dotnet-api-docs/blob/main/xml/System.Security.Claims/ClaimTypes.xml

Document Version Independent Id

20c7c576-2d4c-2085-0330-81abf6af2833

Platform Id

ece51d8f-4b08-c150-0c26-d85f9b637895

Article author

@dotnet-bot

Associated WorkItem - 426127
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Apr 25, 2025
@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Apr 25, 2025
@gewarren
Copy link
Contributor Author

Same for WindowsUserClaim.

@gewarren gewarren added area-System.Security Issues related to security practices for .NET developers. and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Apr 25, 2025
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones

@vcsjones
Copy link
Member

Schema URIs are mostly used as identifiers, and shouldn't be used as actual as actual links. The same is true for most links on

https://learn.microsoft.com/en-us/dotnet/api/system.security.claims.claimtypes

These string values come from actual source and should not be changed. https://github.com/dotnet/runtime/blob/5a0865c7c2ff6b7310d619a0aff376f3b45cb57c/src/libraries/System.Security.Claims/ref/System.Security.Claims.cs#L148

@gewarren gewarren mentioned this issue Apr 25, 2025
Merged
@gewarren gewarren self-assigned this Apr 25, 2025
@gewarren gewarren added the 🗺️ reQUEST Triggers an issue to be imported into Quest. label Apr 25, 2025
@github-project-automation github-project-automation bot moved this from 🔖 Ready to ✅ Done in dotnet/docs April 2025 sprint project Apr 28, 2025
@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Apr 28, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gewarren gewarren

Labels
area-System.Security Issues related to security practices for .NET developers. 📌 seQUESTered Identifies that an issue has been imported into Quest. user-feedback
Projects
dotnet/docs April 2025 sprint project
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clarify that schema URIs aren't hyperlinks gewarren/dotnet-api-docs
2 participants
@vcsjones @gewarren