​

ves-io-schema-oidc_provider-CustomAPI-Replace

Published April 5, 2023 | Last modified September 14, 2026

Examples of performing oidc_provider CustomAPI Replace

Usecase:

Replace google provider

Request:

Request using vesctl:

vesctl request rpc oidc_provider.CustomAPI.Replace -i request.yaml --uri /public/custom/namespaces/system/oidc_providers/google-oidc --http-method POST

where file request.yaml has following contents:

namespace: documentation
spec:
  googleOidcSpecType:
    clientId: new test client id
    clientSecret: client-secret
    hostedDomain: domain-new
  providerType: GOOGLE

vesctl yaml response:

{}

Request using curl:

curl -X 'POST' -d '{"namespace":"documentation","spec":{"provider_type":"GOOGLE","google_oidc_spec_type":{"client_id":"new test client id","client_secret":"client-secret","hosted_domain":"domain-new"}}}' -H 'Content-Type: application/json' -H 'X-Volterra-Useragent: v1/pgm=_var_folders_q2_3kp8z3zs0x5_m7pk1bgb0_ph0000gp_T_go-build1655461974_b001_apidocs.test/host=MTY6VVHQPH/svc=S:examplesvc/site=mytestce01' 'https://acmecorp.console.ves.volterra.io/api/web/custom/namespaces/system/oidc_providers/google-oidc'

curl response:

HTTP/1.1 200 OK
Content-Length: 23
Content-Type: application/json
Date: Fri, 19 Jun 2026 22:03:49 GMT
Vary: Accept-Encoding


{
  "err": "EUNKNOWN"
}
On this page: