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

Fix: 1Pass SCIM Bridge Instructions #700

Merged
merged 2 commits into from
Sep 17, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/layers/ecs/tutorials/1password-scim-bridge.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,14 +29,14 @@ The implementation of this is fairly simple. We will generate credentials for th
1. Click Integrations in the sidebar
1. Select "Set up user provisioning"
1. Choose "Custom"
1. You should now see the SCIM bridge credentials. We will need the "Bearer Token" for the next steps.
1. Save this token in a secure location (such as 1Password) for future reference
1. Store the credentials in AWS SSM Parameter Store. This will allow the ECS task definition to access the credentials securely.
1. You should now see the SCIM bridge credentials. We will need the "scimsession" and "Bearer Token" for the next steps.
1. Save these credentials in a secure location (such as 1Password) for future reference
1. Store only the "scimsession" in AWS SSM Parameter Store. This will allow the ECS task definition to access the credentials securely. Then once the service is running, the server will ask for the bearer token to verify the connection, which we will enter at that time.

<Steps>
- Open the AWS Web Console - Navigate to the target account, such as `core-auto`, and target region, such as `us-west-2`
- Open "AWS System Manager" > "Parameter Store"
- Create a new Secure String parameter using the credentials you generated in the previous step: `/1password/scim/bearer-token`
- Create a new Secure String parameter using the credentials you generated in the previous step: `/1password/scim/scimsession`
</Steps>
</Steps>

Expand Down Expand Up @@ -87,7 +87,7 @@ The implementation of this is fairly simple. We will generate credentials for th
OP_TLS_DOMAIN: ""
OP_CONFIRMATION_INTERVAL: "300"
map_secrets:
OP_SESSION: "1password/scim/bearer-token"
OP_SESSION: "1password/scim/scimsession"
# OP_WORKSPACE_CREDENTIALS: ""
# OP_WORKSPACE_SETTINGS: ""
log_configuration:
Expand Down Expand Up @@ -122,15 +122,15 @@ The implementation of this is fairly simple. We will generate credentials for th
<Step>
### <StepNumber/> Validate the Integration

The final step is to validate the integration. Connect to the VPN (if deployed the ECS service is deployed with a private ALB), navigate to the SCIM bridge URL, and confirm the service is running.
After deploying the SCIM bridge ECS service, verify the service is running and accessible. Connect to the VPN (if deployed the ECS service is deployed with a private ALB), navigate to the SCIM bridge URL, and confirm the service is running.

For example, go to `https://1pass-scim.platform.usw1.auto.core.acme-svc.com/`
</Step>

<Step>
### <StepNumber/> Connect your Identity Provider
### <StepNumber/> Connect your Identity Provider

Finally, connect your identity provider to the SCIM bridge. The SCIM bridge URL will be the URL you validated in the previous step. Follow the instructions in the 1Password SCIM Bridge documentation to connect your identity provider.
Finally, connect your identity provider to the SCIM bridge. The SCIM bridge URL will be the URL you validated in the previous step. Follow the instructions in the 1Password SCIM Bridge documentation to connect your identity provider, using the Bearer Token you generated in the first step.

</Step>

Expand Down
Loading