habsi/authentik
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

website/integrations: all: install -> installation (#12676)

Browse Source 
* website/integrations: all: install -> installation

* fix for new integr 

Signed-off-by: 4d62 <git@sdko.org>

---------

Signed-off-by: 4d62 <git@sdko.org>
This commit is contained in:
4d62
2025-01-16 17:23:22 -05:00
committed by GitHub
parent 4597ee45f8
commit d111740f6b
82 changed files with 144 additions and 144 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
website/integrations/services/nextcloud/index.md
View File

@ -39,8 +39,8 @@ There are 3 ways to setup single sign on (SSO) for Nextcloud:
The following placeholders are used in this guide:
- `nextcloud.company` is the FQDN of the Nextcloud install.
- `authentik.company` is the FQDN of the authentik install.
- `nextcloud.company` is the FQDN of the Nextcloud installation.
- `authentik.company` is the FQDN of the authentik installation.
- `authentik.local` is the internal FQDN of the authentik install (only relevant when running authentik and Nextcloud behind a reverse proxy)
Lets start by thinking what user attributes need to be available in Nextcloud:
@ -228,8 +228,8 @@ If you do not have any relying parties accessing authentik from the outside, you
The following placeholders are used in this guide:
- `nextcloud.company` is the FQDN of the Nextcloud install.
- `authentik.company` is the FQDN of the authentik install.
- `nextcloud.company` is the FQDN of the Nextcloud installation.
- `authentik.company` is the FQDN of the authentik installation.
Create an application in authentik and note the slug you choose, as this will be used later. In the Admin Interface, go to _Applications_ -> _Providers_. Create a _SAML provider_ with the following parameters: