|
|
This section holds Azure specific operating procedure for the open source version of OSDU
|
|
|
|
|
|
## Integrating with Identity Providers
|
|
|
<tbd, runbook, examples for how to integrate with a pre-existing or external identity provider, whether it's Azure specific or other>
|
|
|
OSDU services on Azure run in AKS and use Istio to orchestrate identity validation. The Azure Istio configuration is provided as a [template](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/charts/osdu-istio/templates/authentication.yaml) which can be edited by OSDU providers on Azure or customers and configure to attach to their preferred identity providers. For example, if you are not using AzureAD and prefer to use an identity provider like Okta or Google, you can set the variable ` .Values.global.azure.tenant ` to point to your own identity provider.
|
|
|
|
|
|
## Backup and Restore for OSDU Data
|
|
|
The [Backup/Restore functionality for Azure](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/backup-restore.md) is currently still in development, however [this](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/backup-restore.md) is the target architecture that will be supported in R3.
|
... | ... | |