---
title: "Get a custom identity provider for the current organization"
method: GET
path: "/organization/identity_provider/{name}"
---

# Get a custom identity provider for the current organization

`GET /organization/identity_provider/{name}`

## Request

- Base URL: `https://api.border0.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.border0.com/organization/identity_provider/{name}`
- Auth: API key in header `Authorization`

## Path parameters

- `name` string, required

## Response `200`

OK

- V1GetIdentityProviderResponse
  - `display_name` string
  - `enabled` boolean
  - `google_workspace_configuration` ModelsGoogleWorkspaceIdentityProviderConfig
    - `client_id` string: An identifier which uniquely identifies border0 as a client of the Google Workspace account. You get this and the client secret when you create an "App Integration" in the Google API Console. This is typically of the form ${GIBBERISH}.apps.googleusercontent.com
    - `client_secret` string: Secret to authenticate with Google Workspace.
    - `google_workspace_domain` string: Domain of the Google Workspace
  - `id` string: unique identifier for identity provider / connection
  - `logo_url` string
  - `name` string
  - `oidc_configuration` ModelsOpenIDConnectIdentityProviderConfig
    - `client_id` string: An identifier which uniquely identifies border0 as a client of the OpenID Connect provider.
    - `client_secret` string: A per-client secret generated by the identity provider. It is used by the client to exchange OAuth2.0 auth codes for ID Tokens issued by the identity provider.
    - `discovery_url` string: URL of the discovery document of the OpenID Connect provider.
    - `oidc_flow_type` string: FlowType determines the way in which the oidc provider will transmit ID Tokens to border0's IDP. Front Channel will use OIDC protocol with response_mode=form_post and response_type=id_token. Back Channel will use response_type=code. See https://darutk.medium.com/diagrams-of-all-the-openid-connect-flows-6968e3990660 for more.
  - `okta_workforce_configuration` ModelsOktaWorksforceIdentityProviderConfig
    - `client_id` string: An identifier which uniquely identifies border0 as a client of the Okta Workforce account. You get this and the client secret when you create an "App Integration" in Okta.
    - `client_secret` string: Secret to authenticate with Okta.
    - `okta_domain` string: Okta domain for Okta Workforce account e.g. mydomain.okta.com
  - `saml_configuration` ModelsSAMLIdentityProviderConfig
    - `request_protocol_binding` string: The protocol to use for SAML assertion request binding, one of [ "HTTP-POST", "HTTP-Redirect" ]. Note that the value of this field is shorthand, full value is of the form: "urn:oasis:names:tc:SAML:2.0:bindings:{REQUEST_PROTOCOL_BINDING_SHORTHAND}"
    - `request_signing_algorithm` string: Algorithm to use for assertion request signing, one of [ "rsa-sha256", "rsa-sha1" ].
    - `request_signing_digest_algorithm` string: Algorithm to use for the assertion request signing digest (hash), one of [ "sha256", "sha1" ].
    - `request_signing_enabled` boolean: Whether to have the SAML assertion consumer (border0) sign the assertion request.
    - `request_template` string: The template for the SAML assertion request. It may include any/all/none of the following parameters: - "@@AssertServiceURLAndDestination@@" - "@@ID@@" - "@@IssueInstant@@" - "@@ProtocolBinding@@" - "@@Issuer@@" Example Template (ignore the dashes '-'): -------------------------------------------------------------------------------------------- <samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" @@AssertServiceURLAndDestination@@ ID="@@ID@@" IssueInstant="@@IssueInstant@@" ProtocolBinding="@@ProtocolBinding@@" Version="2.0"> <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">@@Issuer@@</saml:Issuer> </samlp:AuthnRequest> --------------------------------------------------------------------------------------------
    - `sign_in_url` string: The SAML provider's sign-in URL (where users are redirected to)
    - `signing_certificate` string: The x509 certificate (public key) corresponding to the SAML provider's assertion signing (private) key.
  - `type` string

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `404`: Not Found
- `500`: Internal Server Error

---

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