Added changesets

server/routerlicious/.changeset/curly-wombats-peel.md

@@ -0,0 +1,7 @@
+---
+"@fluidframework/server-services-utils": minor
+---
+
+Adds support for a new token claim - `isKeylessAccessToken`.
+
+The added support for this new claim would allow the server to know what keys to use to validate an access token. This value will only be added for tokens signed by the server. It is not exposed to the client API.

server/routerlicious/.changeset/six-candles-sneeze.md

@@ -0,0 +1,7 @@
+---
+"@fluidframework/server-services": minor
+---
+
+Adds support for the tenant manager to use Riddlers new APIs
+
+Now the tenant manager used by Alfred can fetch the new private keys exposed by Riddler. The `getKeys` can be called with the `usePrivateKeys` flag set to true. This is currently only used for one Alfred to Riddler API call to fetch tenant keys when signing a document creation token.

server/routerlicious/.changeset/weak-radios-camp.md

@@ -0,0 +1,7 @@
+---
+"@fluidframework/server-routerlicious-base": major
+---
+
+Now Riddler supports using private keys to sign server access tokens
+
+Riddler's tenant manager now exposed two new properties - `enablePrivateKeyAccess` and `enableSharedKeyAccess`. These respectively indicate whether a tenant can be accessed using hidden private keys and whether a tenant can be accessed using shared secrets. The APIs added support toggling the `enablePrivateKeyAccess` prop. They also support fetching these new keys and refreshing these new keys. All calls to manipulate private keys should be made from witin the server.

server/routerlicious/.changeset/wide-ducks-bake.md

@@ -0,0 +1,7 @@
+---
+"@fluidframework/server-services-core": major
+---
+
+Adds new props to the tenant interface to support private key based access
+
+Now tenants have two new properties - `enablePrivateKeyAccess` and `enableSharedKeyAccess`. These are used by Riddler to determine whether a tenant allows just shared key access, private key access or both.