Add role checking to identity context

[Copilot]

Summary

Adds role-based access control primitives to the identity system, enabling frontend components to check user roles.

Added

• roles property on IdentityProviderResult (backend) and IIdentity interface (frontend) containing array of role names
• isInRole(role: string) method on IIdentity for role membership checks
• Backend role extraction from ClaimTypes.Role claims in IdentityProviderResultHandler
• Documentation examples for both React and core identity providers

Usage:

import { useIdentity } from '@cratis/arc.react/identity';

export const AdminPanel = () => {
    const identity = useIdentity();
    
    if (!identity.isInRole('Admin')) {
        return <div>Access denied</div>;
    }
    
    return <div>Admin content</div>;
};

Roles default to empty array when not present, maintaining backward compatibility.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• docs.fluentvalidation.net
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• docs.microsoft.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• example.com
  • Triggering command: /opt/hostedtoolcache/node/24.13.0/x64/bin/node /opt/hostedtoolcache/node/24.13.0/x64/bin/node /home/REDACTED/work/Arc/Arc/node_modules/vitest/vitest.mjs run (dns block)
• http://nuget.org:80/packages/Cratis.Arc
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (http block)
• img.shields.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• learn.microsoft.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• marketplace.visualstudio.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• martinfowler.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• mobx.js.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• modheader.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• primereact.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• www.base64encode.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• www.npmjs.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)
• www.nuget.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/a07aeef48358ad48/node_modules/.bin/linkinator Documentation/**/*.md --markdown --recurse --verbosity error --status-code 403:ok (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add a way to check if a user / principal is in role for React frontend</issue_title>
<issue_description>useIdentity() returns an IIdentityContext it would be nice to have a isInRole() method on it.

This entails adding roles as an Innumerable on the IdentityProviderResult in both the backend and string array in the frontend version. On the Identity in the frontend we should then have isInRole() method that takes the role and returns true or false.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add a way to check if a user / principal is in role for React frontend #184

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.