The goal of this change is to make it easy to integrate Authentik SSO in the CoopCloud recipe for Writefreely.
I've shamelessly copied the way Nextcloud implements its integration with Authentik to achieve this.
This change goes hand in hand with a separate Pull Request to be submitted into the Writefreely recipe repository [EDIT: added coop-cloud/writefreely#7]. I've included some documentation in there as well.
The end result should look something like this (from the perspective of Authentik):
Following the documentation on Writefreely's side you'd get a nice Sign in with Authentik button when you go to the /login endpoint.
The goal of this change is to make it easy to integrate Authentik SSO in the CoopCloud recipe for Writefreely.
I've shamelessly copied the way Nextcloud implements its integration with Authentik to achieve this.
This change goes hand in hand with a separate Pull Request to be submitted into the Writefreely recipe repository [EDIT: added https://git.coopcloud.tech/coop-cloud/writefreely/pulls/7]. I've included some documentation in there as well.
The end result should look something like this (from the perspective of Authentik):

Following the documentation on Writefreely's side you'd get a nice `Sign in with Authentik` button when you go to the `/login` endpoint.
The structure of the blueprints changed a bit. You can use https://git.coopcloud.tech/coop-cloud/authentik/src/branch/main/nextcloud.yaml.tmpl as template. For example the slug is now used as identifiers and the name and description is set by an env.
I'm sorry, I've missed this PR. In the meantime the blueprint structure changed a bit.
Thank you for contributing :)
No worries! Thanks for the review.
I've applied the changes you suggested.
> I'm sorry, I've missed this PR. In the meantime the blueprint structure changed a bit.
> Thank you for contributing :)
No worries! Thanks for the review.
I've applied the changes you suggested.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The goal of this change is to make it easy to integrate Authentik SSO in the CoopCloud recipe for Writefreely.
I've shamelessly copied the way Nextcloud implements its integration with Authentik to achieve this.
This change goes hand in hand with a separate Pull Request to be submitted into the Writefreely recipe repository [EDIT: added coop-cloud/writefreely#7]. I've included some documentation in there as well.
The end result should look something like this (from the perspective of Authentik):
Following the documentation on Writefreely's side you'd get a nice
Sign in with Authentikbutton when you go to the/loginendpoint.I'm sorry, I've missed this PR. In the meantime the blueprint structure changed a bit.
Thank you for contributing :)
@@ -0,0 +43,4 @@conditions: []id: writefreely_provideridentifiers:pk: 9988Can you change this id to another unique id. It's a duplicate with monitoring-ng.
@@ -0,0 +56,4 @@conditions: []id: writefreely_applicationidentifiers:name: WritefreelyThe structure of the blueprints changed a bit. You can use https://git.coopcloud.tech/coop-cloud/authentik/src/branch/main/nextcloud.yaml.tmpl as template. For example the slug is now used as identifiers and the name and description is set by an env.
No worries! Thanks for the review.
I've applied the changes you suggested.