update readme with authentik integration guide

This commit is contained in:
many 2025-04-09 16:48:43 -04:00
parent ddd833b908
commit 4ef2ddd223

View File

@ -19,17 +19,19 @@
* `abra app new civicrm-wordpress`
* `abra app config <app-name>`
Generate secrets (be sure to save them):
* `abra app secret g <app-name> db_root_password v1`
* `abra app secret g <app-name> db_password v1`
* `abra app secret g <app-name> civicrm_site_key v1`
* `abra app secret g <app-name> civicrm_cred_key v1`
* `abra app secret g <app-name> civicrm_sign_key v1`
Authentik integration:
* When configuring, uncomment `COMPOSE_FILE`, `OPEN_ID_CLIENT_ID`, `SECRET_OPEN_ID_CLIENT_SECRET_VERSION`, and `AUTHENTIK_DOMAIN`
* To configure your Authentik deployment, follow the guide at [`docs.goauthentik.io/integrations/services/wordpress`](https://docs.goauthentik.io/integrations/services/wordpress/).
* NOTE: at the time of writing the Authentik integration guide incorrectly says to set the redirect URI to `https://wp.company/admin-ajax.php?action=openid-connect-authorize` when it should be `https://wp.company/wp-admin/admin-ajax.php?action=openid-connect-authorize`
* If using a different OpenID provider, leave `AUTHENTIK_DOMAIN` commented and uncomment the other OpenID configuration options
Insert secrets:
* `abra app secret i <app-name> wordpress_admin_password v1 '<temp account password>'`
* `abra app secret i <app-name> smtp_password v1 '<smtp password>'`
Generate secrets (be sure to save them):
* `abra app secret g -a <app-name>`
Deploy app:
* `abra app deploy <app-name>`