website/integrations: remove placeholders from AWS setup (#6021)

* Update index.md

removing irrelevant line for this type of AWS setup

Signed-off-by: jsiegel-supplyframe <120349776+jsiegel-supplyframe@users.noreply.github.com>

* remove other unused placeholder too

Signed-off-by: Jens Langhammer <jens@goauthentik.io>

---------

Signed-off-by: jsiegel-supplyframe <120349776+jsiegel-supplyframe@users.noreply.github.com>
Signed-off-by: Jens Langhammer <jens@goauthentik.io>
Co-authored-by: Jens Langhammer <jens@goauthentik.io>
This commit is contained in:
jsiegel-supplyframe 2023-06-21 04:43:51 -07:00 committed by GitHub
parent bd9bf59073
commit 9519c4023e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 10 deletions

View File

@ -19,10 +19,6 @@ This all depends on your preference and needs.
## Preparation ## Preparation
The following placeholders will be used:
- `authentik.company` is the FQDN of the authentik install.
Create an application in authentik and note the slug, as this will be used later. Create a SAML provider with the following parameters: Create an application in authentik and note the slug, as this will be used later. Create a SAML provider with the following parameters:
- ACS URL: `https://signin.aws.amazon.com/saml` - ACS URL: `https://signin.aws.amazon.com/saml`
@ -87,12 +83,6 @@ return user.username
## Preparation ## Preparation
The following placeholders are used:
- `authentik.company` is the FQDN of the authentik install.
Additional Preparation:
- A certificate to sign SAML assertions is required. You can use authentik's default certificate, or provide/generate one yourself. - A certificate to sign SAML assertions is required. You can use authentik's default certificate, or provide/generate one yourself.
- You may pre-create an AWS application. - You may pre-create an AWS application.