---
title: "Update details about a SSO provider."
method: PUT
path: "/admin/sso/providers/{ssoProviderId}"
tags: ["admin"]
---

# Update details about a SSO provider.

`PUT /admin/sso/providers/{ssoProviderId}`

You can only update only one of `metadata_url` or `metadata_xml` at once. The SAML Metadata represented by these updates must advertize the same Identity Provider EntityID. Do not include the `domains` or `attribute_mapping` property to keep the existing database values.

## Request body

- object
  - `metadata_url` string, uri
  - `metadata_xml` string
  - `domains` string[]
  - `attribute_mapping` SAMLAttributeMappingSchema
    - `keys` object

## Response `200`

SSO provider details were updated.

- SSOProviderSchema
  - `id` string, uuid
  - `sso_domains` object[]
    - `domain` string, hostname
  - `saml` object
    - `entity_id` string
    - `metadata_xml` string
    - `metadata_url` string
    - `attribute_mapping` SAMLAttributeMappingSchema
      - `keys` object

## Other responses

- `400` — HTTP Bad Request response. Can occur if the passed in JSON cannot be unmarshalled properly or when CAPTCHA verification was not successful. In certain cases can also occur when features are disabled on the server (e.g. sign ups). It may also mean that the operation failed due to some constraint not being met (such a user already exists for example).
- `401` — HTTP Unauthorized response.
- `403` — HTTP Forbidden response.
- `404` — A provider with this UUID does not exist.

---

[API](https://skmtc.net/supabase/apis/supabase-auth-rest-api.md) · [All operations](https://skmtc.net/supabase/apis/supabase-auth-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/supabase/supabase-auth-rest-api/versions/2664b89bee49/schema)