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

feat: allow alternative audience for server #371

Merged
merged 2 commits into from
Feb 13, 2025
Merged

Conversation

alanshaw
Copy link
Member

This PR adds a new server option audience, which allows the server to accept invocations for audiences other than the service itself.

This option was already available (and continues to be available) on a per handler basis (via provideAdvanced), it takes precedence over the new global server audience.

Concretely, the DID for web3.storage is changing, but we want to be able to accept invocations targeting the old DID without having to configure every single handler.

Copy link
Member

@fforbeck fforbeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@alanshaw alanshaw merged commit d793091 into main Feb 13, 2025
42 of 47 checks passed
@alanshaw alanshaw deleted the feat/server-alt-audience branch February 13, 2025 14:00
@github-actions github-actions bot mentioned this pull request Feb 13, 2025
volmedo added a commit to storacha/go-ucanto that referenced this pull request Feb 26, 2025
Part of #35

This PR ports the changes added to the JS ucanto library here:
storacha/ucanto#371

It adds a new `WithAlternativeAudiences` option that can be used when
creating the server to have it accept invocations targeted to audiences
different from the server's main identity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants