scim-examples icon indicating copy to clipboard operation
scim-examples copied to clipboard

1Password SCIM Bridge deployment examples

Results 8 scim-examples issues
Sort by recently updated
recently updated
newest added

This PR is to establish a new Cloud Run deployment example for SCIM Bridge, including: - Cloud Run service YAML - README with steps to deploy SCIM Bridge using Cloud...

enhancement

1Password SCIM example - ECS|Fargate deployment Adding an option to add SSL policy to fix insecure TLS issue The previous version uses old SSL Policy (ELBSecurityPolicy-2016-08)

This issue is to track a few fairly minor issues with our [AWS Terraform deployment example](https://github.com/1Password/scim-examples/tree/master/aws-ecsfargate-terraform): - [ ] Public subnets are not consistently tagged in such a way that...

enhancement

Specifically, [Step 3.3](https://github.com/1Password/scim-examples/blob/da40c2b5d6864e9203e55664d7aafe8e59636db8/azure-container-apps/README.md#step-3-deploy-the-scim-bridge-container): > 3. Choose "Volume mounts", then click "Create new volume" below Secrets. Adjust the following: > - **Volume type**: Choose Secret. > - **Name**: Enter `credentials`. >...

documentation

This PR updates the base configuration for the Redis instance included as part of our example SCIM Bridge deployments. Container configuration varies by platform, but the strategy is similar for...

Our current CloudFormation template automates DNS record management using Amazon Route 53 for the records that are required: - to valid ownership of the domain used with AWS Certificate Manager...

enhancement

When using our CloudFormation template, ECS cluster creation may fail if the ExecutionRole resource has not been created. Example error: ```sh Invalid request provided: CreateCluster Invalid Request: Unable to assume...

Under the [self-managed-tls](https://github.com/1Password/scim-examples/tree/4b38853c38e03b33997d36e9e4f6ccb3d3737df2/kubernetes#self-managed-tls) section it says: > Traffic from your TLS endpoint should be directed to this port (80, by default) From my understanding that's wrong. The deployment is configured...

documentation