Global, shared secrets on the server level #431

New Issue

decentral1se · 2023-03-06T13:55:45Z

decentral1se commented

2023-03-06 13:55:45 +00:00

You configure app A at foo_com and app B at bar_com. Then both need a shared secret. You generate and insert both with abra app foo_com secret insert ... and abra app bar_com secret insert ... but what if we could share a common secret across the two apps? It's already possible, you can reference a shared_smtp_secret_v1 between both apps if you reference this in your configuration by name. We could have a abra servers secret ... interface for creating these? Unsure. Also, not sure how we can reference these shared secrets when there are already secrets referenced in existing configuration that are not shared. You might already have a ${STACK_NAME}_smtp_pass_${SMTP_PASS_VERSION} in a recipe config? I think those were the thoughts! /cc @moritz

You configure app A at `foo_com` and app B at `bar_com`. Then both need a shared secret. You generate and insert both with `abra app foo_com secret insert ...` and `abra app bar_com secret insert ...` but what if we could share a common secret across the two apps? It's already possible, you can reference a `shared_smtp_secret_v1` between both apps if you reference this in your configuration by name. We could have a `abra servers secret ...` interface for creating these? Unsure. Also, not sure how we can reference these shared secrets when there are already secrets referenced in existing configuration that are not shared. You might already have a `${STACK_NAME}_smtp_pass_${SMTP_PASS_VERSION}` in a recipe config? I think those were the thoughts! /cc @moritz

decentral1se added the

enhancement

label 2023-03-06 13:55:45 +00:00

decentral1se commented

2023-03-24 08:38:14 +00:00

@3wordchant and myself ran into another group (WASHNote) needing this. They have to deploy several instances of the same app and need a shared client secret for SSO. Would greatly simplify the deployment if we can get a convention going for this technique.

decentral1se added the

documentation

label 2024-03-27 06:39:31 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#431