-
Notifications
You must be signed in to change notification settings - Fork 516
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
Per Tenant setting: requests-through-public-did #2572
Comments
Thanks — this is correct. @esune — is there a pattern/approach for making configuration parameters tenant-specific vs. global? |
We have implemented an endpoint in a Traction plugin to facilitate setting these at runtime: see this. I believe that anything listed in this map is supported: we started with a subset of all the options that were available as there are several and we were not sure whether this would be useful for us only or others. I think if there are other flags that would be good to have set at a tenant level they just need to be added to that list. c.c.: @shaangill025 for more insight. |
@esune , is there a plan to add this |
Looping-in @swcurran and @dbluhm for additional opinions. I don't think it is planned, but I don;t see an issue in having that setting be part of the per-tenant customizations. |
Agree. I’m hoping it is well documented how to make a setting a per tenant setting so that we can easily add new ones that make sense. Agree that this is one. |
Since I can define per tenant the setting
public_invites
, it would be great that I could also set per tenant therequests-through-public-did
(in a case where I have a tenant that wants to receive those public did requests, but all other tenants don't).The text was updated successfully, but these errors were encountered: