Skip to content

Commit 7164fa8

Browse files
committed
fix: prettier linting
1 parent 6f87b5b commit 7164fa8

1 file changed

Lines changed: 11 additions & 12 deletions

File tree

README.md

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -237,18 +237,17 @@ The environment is accessible through the following URLs:
237237
<details>
238238
<summary><strong>Requirements for deploying the SPA</strong></summary>
239239

240-
> ### Deploying a Keycloak Instance for Built-in Users Authentication
241-
>
242-
> To enable authentication for Dataverse built-in user accounts in the SPA, you must deploy a Keycloak instance as an OIDC authentication provider and broker for the SPA.
243-
>
244-
> However, using Keycloak is not mandatory. If you do not require authentication for Dataverse built-in users, you can use any OIDC provider to handle user authentication in the SPA.
245-
>
246-
> For supporting built-in users, Keycloak must be properly configured and integrated with the Dataverse backend using the [Dataverse Built-in Users SPI][dv_repo_builtin_users_spi_provider].
247-
>
248-
> On the SPA side, ensure that the PKCE environment variables are set up to connect to the chosen OIDC provider for authentication.
249-
>
250-
> Additionally, to allow the SPI to authenticate users against the Dataverse database, the Dataverse database must be accessible from the Keycloak service within the deployed infrastructure.
251-
240+
> ### Deploying a Keycloak Instance for Built-in Users Authentication
241+
>
242+
> To enable authentication for Dataverse built-in user accounts in the SPA, you must deploy a Keycloak instance as an OIDC authentication provider and broker for the SPA.
243+
>
244+
> However, using Keycloak is not mandatory. If you do not require authentication for Dataverse built-in users, you can use any OIDC provider to handle user authentication in the SPA.
245+
>
246+
> For supporting built-in users, Keycloak must be properly configured and integrated with the Dataverse backend using the [Dataverse Built-in Users SPI][dv_repo_builtin_users_spi_provider].
247+
>
248+
> On the SPA side, ensure that the PKCE environment variables are set up to connect to the chosen OIDC provider for authentication.
249+
>
250+
> Additionally, to allow the SPI to authenticate users against the Dataverse database, the Dataverse database must be accessible from the Keycloak service within the deployed infrastructure.
252251
253252
</details>
254253

0 commit comments

Comments
 (0)