---
title: "Update enterprise connection"
method: PUT
path: "/organization/{organizationId}/enterpriseconnection/{connectionName}"
tags: ["Organization Enterprise Connection"]
---

# Update enterprise connection

`PUT /organization/{organizationId}/enterpriseconnection/{connectionName}`

## Request

- Base URL: `https://api.qovery.com`
- URL: `https://api.qovery.com/organization/{organizationId}/enterpriseconnection/{connectionName}`
- Auth: one of:
  - API key in header `Authorization`
  - HTTP bearer
- TypeScript: <https://skmtc.dev/qovery/apis/qovery-api/docs/organization/:organizationId/enterpriseconnection/:connectionName/put.ts> (a function with typed inputs; its response is checked against the schema)

## Path parameters

- `organizationId` string, uuid, required
- `connectionName` string, required

## Request body

- EnterpriseConnectionDto
  - `default_role` string, required: The purpose of this default role is to be associated to your users if: - you choose to not expose your IDPs groups to the SAML / OIDC connection - no associated group is found in your `group_mappings` defined You can define either a Qovery provided role (i.e `viewer`) or one of your custom role`s uuid.
  - `enforce_group_sync` boolean, required: * if `true`, roles will be synchronized at each user login according to your `group_mappings` configuration based on your IDP groups * if `false`, no synchronization is done for your users and `group_mappings` configuration will be ignored
  - `group_mappings` object, required: This will allow to create mapping rules based on your IDP group names. It's a dictionnary having: - key: either a Qovery provided role (i.e `viewer`) or one of your custom role`s uuid - value: an array of your IDP group names Example: "I want to associate the Qovery role `devops` to my IDP groups ['Administrators', 'DevSecOps']"

## Response `200`

Update enterprise connection

- EnterpriseConnectionDto
  - `default_role` string, required: The purpose of this default role is to be associated to your users if: - you choose to not expose your IDPs groups to the SAML / OIDC connection - no associated group is found in your `group_mappings` defined You can define either a Qovery provided role (i.e `viewer`) or one of your custom role`s uuid.
  - `enforce_group_sync` boolean, required: * if `true`, roles will be synchronized at each user login according to your `group_mappings` configuration based on your IDP groups * if `false`, no synchronization is done for your users and `group_mappings` configuration will be ignored
  - `group_mappings` object, required: This will allow to create mapping rules based on your IDP group names. It's a dictionnary having: - key: either a Qovery provided role (i.e `viewer`) or one of your custom role`s uuid - value: an array of your IDP group names Example: "I want to associate the Qovery role `devops` to my IDP groups ['Administrators', 'DevSecOps']"

## Other responses

- `401`: Access token is missing or invalid
- `403`: Access forbidden
- `404`: Resource not found

---

[API](https://skmtc.dev/qovery/apis/qovery-api.md) - [All operations](https://skmtc.dev/qovery/apis/qovery-api/llms.txt) - [OpenAPI document](https://skmtc.dev/qovery/apis/qovery-api/revisions/93c4960a44ba?raw)