/auth/sso/callback/okta. For instance, if your console lives at
https://console.tiledb.example.com/, the redirect URI should be
https://console.tiledb.example.com/auth/sso/callback/okta. You may optionally add your console’s home page as a sign-out redirect URI, for example
https://console.tiledb.example.com/. Leave Trusted origins empty.
values.yaml. The Client ID and Client Secret go in the
tiledb-cloud-uisection, and the domain also goes in the
.../v1/scim/2.0/. For example, if your TileDB Cloud API server is located at
https://api.tiledb.example.com/, its SCIM endpoint is
SCIMPasswordslist, so it contains
['old password', 'new password']
SCIMPasswordsand deployed your TileDB Cloud installation, the SCIM endpoints are available to Okta. You then need to configure your Okta installation to provision users and groups in TileDB Cloud as desired.
/v1/scim/2.0/on your TileDB API server, as described earlier. The result should look like
SCIMPasswordssection of your TileDB Cloud configuration.