site: reorganize /howto/idp->/howto/supervisor
This commit is contained in:
Benjamin A. Petersen
parent
f632698568
commit
bb670249cf
@ -5,10 +5,10 @@ cascade:
|
||||
menu:
|
||||
docs:
|
||||
name: Supervisor Configuration
|
||||
identifier: howto-configure-idps
|
||||
identifier: howto-configure-supervisor
|
||||
weight: 60
|
||||
---
|
||||
|
||||
These how-to guides show you how to install and configure Pinniped with specific identity providers:
|
||||
|
||||
{{< docsmenu "howto-configure-idps" >}}
|
||||
{{< docsmenu "howto-configure-supervisor" >}}
|
||||
@ -7,7 +7,7 @@ menu:
|
||||
docs:
|
||||
name: With Active Directory
|
||||
weight: 150
|
||||
parent: howto-configure-idps
|
||||
parent: howto-configure-supervisor
|
||||
aliases:
|
||||
- /docs/howto/configure-supervisor-with-activedirectory/
|
||||
---
|
||||
@ -7,7 +7,7 @@ menu:
|
||||
docs:
|
||||
name: With Auth0 OIDC
|
||||
weight: 80
|
||||
parent: howto-configure-idps
|
||||
parent: howto-configure-supervisor
|
||||
aliases:
|
||||
- /docs/howto/configure-supervisor-with-auth0/
|
||||
---
|
||||
@ -7,7 +7,7 @@ menu:
|
||||
docs:
|
||||
name: With Dex OIDC
|
||||
weight: 80
|
||||
parent: howto-configure-idps
|
||||
parent: howto-configure-supervisor
|
||||
aliases:
|
||||
- /docs/howto/configure-supervisor-with-dex/
|
||||
---
|
||||
@ -7,7 +7,7 @@ menu:
|
||||
docs:
|
||||
name: With GitLab OIDC
|
||||
weight: 90
|
||||
parent: howto-configure-idps
|
||||
parent: howto-configure-supervisor
|
||||
aliases:
|
||||
- /docs/howto/configure-supervisor-with-gitlab/
|
||||
---
|
||||
@ -7,7 +7,7 @@ menu:
|
||||
docs:
|
||||
name: With JumpCloud LDAP
|
||||
weight: 110
|
||||
parent: howto-configure-idps
|
||||
parent: howto-configure-supervisor
|
||||
aliases:
|
||||
- /docs/howto/configure-supervisor-with-jumpcloudldap/
|
||||
---
|
||||
@ -7,7 +7,7 @@ menu:
|
||||
docs:
|
||||
name: With Okta OIDC
|
||||
weight: 80
|
||||
parent: howto-configure-idps
|
||||
parent: howto-configure-supervisor
|
||||
aliases:
|
||||
- /docs/howto/configure-supervisor-with-okta/
|
||||
---
|
||||
@ -7,7 +7,7 @@ menu:
|
||||
docs:
|
||||
name: With OpenLDAP
|
||||
weight: 100
|
||||
parent: howto-configure-idps
|
||||
parent: howto-configure-supervisor
|
||||
aliases:
|
||||
- /docs/howto/configure-supervisor-with-openldap/
|
||||
---
|
||||
@ -7,7 +7,7 @@ menu:
|
||||
docs:
|
||||
name: With Workspace ONE Access
|
||||
weight: 80
|
||||
parent: howto-configure-idps
|
||||
parent: howto-configure-supervisor
|
||||
aliases:
|
||||
- /docs/howto/configure-supervisor-with-workspace_one_access/
|
||||
---
|
||||
@ -7,7 +7,7 @@ menu:
|
||||
docs:
|
||||
name: As an OIDC Issuer
|
||||
weight: 10
|
||||
parent: howto-configure-idps
|
||||
parent: howto-configure-supervisor
|
||||
aliases:
|
||||
- /docs/howto/configure-supervisor/
|
||||
---
|
||||
@ -101,7 +101,7 @@ had to make some choices. The choices made for this tutorial were:
|
||||
- For web-based login flows as used by OIDC identity providers, the Pinniped Supervisor needs TLS certificates
|
||||
that are trusted by the end users' web browsers. There are many ways to create TLS certificates.
|
||||
There are also several ways to configure the TLS certificates on the Supervisor, as described in the
|
||||
[docs for configuring the Supervisor]({{< ref "../howto/idps/configure-supervisor" >}}).
|
||||
[docs for configuring the Supervisor]({{< ref "../howto/supervisor/configure-supervisor" >}}).
|
||||
For this tutorial we will use [Let's Encrypt](https://letsencrypt.org) with [cert-manager](https://cert-manager.io/docs/),
|
||||
because any reader could use these services if they would like to try these steps themselves.
|
||||
- The Pinniped Concierge can be installed in many types of Kubernetes clusters, as described in
|
||||
@ -198,7 +198,7 @@ kubectl apply \
|
||||
### Create a LoadBalancer Service for the Supervisor
|
||||
|
||||
There are several options for exposing the Supervisor's endpoints outside the cluster, which are described in the
|
||||
[howto guide for configuring the Supervisor]({{< ref "../howto/idps/configure-supervisor" >}}). For this tutorial,
|
||||
[howto guide for configuring the Supervisor]({{< ref "../howto/supervisor/configure-supervisor" >}}). For this tutorial,
|
||||
we will use a public LoadBalancer.
|
||||
|
||||
Create a LoadBalancer to expose the Supervisor's endpoints to the public, being careful to only
|
||||
@ -408,7 +408,7 @@ The general steps required to create and configure a client in Okta are:
|
||||
3. Create a test user with an email and a password. It does not need to be a real email address for the purposes of this tutorial.
|
||||
4. Create an app in the Okta UI.
|
||||
1. For more information about creating an app in the Okta UI, see the
|
||||
[Configure Supervisor With Okta OIDC howto doc]({{< ref "../howto/idps/configure-supervisor-with-okta" >}}).
|
||||
[Configure Supervisor With Okta OIDC howto doc]({{< ref "../howto/supervisor/configure-supervisor-with-okta" >}}).
|
||||
2. Make sure that the test user is assigned to the app in the app's "Assignments" tab.
|
||||
3. Add the FederationDomain's callback endpoint to the "Sign-in redirect URIs" list on the app in the UI.
|
||||
The callback endpoint is the FederationDomain's issuer URL plus `/callback`,
|
||||
|
||||
@ -111,7 +111,7 @@ And it is important that your users are using authentic kubeconfig files handed
|
||||
### How to use LDAP with your Pinniped Supervisor
|
||||
|
||||
Once you have [installed]({{< ref "docs/howto/install-supervisor.md" >}})
|
||||
and [configured]({{< ref "docs/howto/idps/configure-supervisor.md" >}}) the Supervisor, adding an LDAP provider is as easy as creating
|
||||
and [configured]({{< ref "docs/howto/supervisor/configure-supervisor.md" >}}) the Supervisor, adding an LDAP provider is as easy as creating
|
||||
an [LDAPIdentityProvider](https://github.com/vmware-tanzu/pinniped/blob/main/generated/1.20/README.adoc#ldapidentityprovider) resource.
|
||||
|
||||
We've provided examples of using [OpenLDAP]({{< ref "docs/howto/install-supervisor.md" >}})
|
||||
|
||||
@ -23,7 +23,7 @@ Our initial LDAP implementation released with v.10.0 can be used to work with an
|
||||
|
||||
Pinniped Supervisor authenticates your users with the AD provider via the LDAP protocol, and then issues unique, short-lived, per-cluster tokens. Our previous blog post on [LDAP configuration]({{< ref "2021-06-02-first-ldap-release.md">}}), elaborates on the security considerations to support integration at the Pinniped Supervisor level instead of at the Concierge.
|
||||
|
||||
To setup the AD configuration, once you have Supervisor configured with ingress [installed the Pinniped Supervisor]({{< ref "docs/howto/install-supervisor.md" >}}) and you have [configured a FederationDomain]({{< ref "docs/howto/idps/configure-supervisor" >}}) to issue tokens for your downstream clusters, you can create an [ActiveDirectoryIdentityProvider](https://github.com/vmware-tanzu/pinniped/blob/main/generated/1.20/README.adoc#activedirectoryidentityprovider) in the same namespace as the Supervisor.
|
||||
To setup the AD configuration, once you have Supervisor configured with ingress [installed the Pinniped Supervisor]({{< ref "docs/howto/install-supervisor.md" >}}) and you have [configured a FederationDomain]({{< ref "docs/howto/supervisor/configure-supervisor" >}}) to issue tokens for your downstream clusters, you can create an [ActiveDirectoryIdentityProvider](https://github.com/vmware-tanzu/pinniped/blob/main/generated/1.20/README.adoc#activedirectoryidentityprovider) in the same namespace as the Supervisor.
|
||||
Here’s what an example configuration looks like
|
||||
|
||||
```yaml
|
||||
@ -60,7 +60,7 @@ Here’s what an example configuration looks like
|
||||
password: "YOUR_PASSWORD"
|
||||
```
|
||||
|
||||
You can also customize the userSearch and groupSearch as shown in the examples in our reference documentation [here]({{< ref "docs/howto/idps/configure-supervisor-with-activedirectory.md" >}})
|
||||
You can also customize the userSearch and groupSearch as shown in the examples in our reference documentation [here]({{< ref "docs/howto/supervisor/configure-supervisor-with-activedirectory.md" >}})
|
||||
|
||||
In the above example, users will be able to login with either their sAMAccountName (i.e. pinny), userPrincipalName (i.e. pinny@example.com) or mail attribute. This reduces the need to tell users what specific value from AD must be provided in the username field. Regardless of what value the user provides in the username field, the userPrincipalName will be used as the identity in Kubernetes clusters. UPN is used as the username attribute by default as it is unique within an AD forest. Similarly, a UPN is generated for each group using its sAMAccountName attribute and the AD domain hostname. The default AD configuration finds both direct and nested groups.
|
||||
|
||||
|
||||
@ -61,7 +61,7 @@ spec:
|
||||
allowPasswordGrant: false
|
||||
```
|
||||
|
||||
Refer to a more complete example for configuring Okta at [how to configure Okta as IDP with Supervisor]({{< ref "docs/howto/idps/configure-supervisor-with-okta.md" >}}).
|
||||
Refer to a more complete example for configuring Okta at [how to configure Okta as IDP with Supervisor]({{< ref "docs/howto/supervisor/configure-supervisor-with-okta.md" >}}).
|
||||
|
||||
Inside Okta, when you create the Application, make sure to select refresh tokens as the Grant type along with Authorization code. See below:
|
||||
|
||||
|
||||
@ -41,7 +41,7 @@ For more information on this feature refer to [#981](https://github.com/vmware-t
|
||||
|
||||
We continue to gather feedback from the community around the need to integrate with different Identity Providers. With this in mind, we have documented our support for configuring [VMware Workspace ONE Access](https://www.vmware.com/products/workspace-one/access.html) (formerly VMware Identity Manager) as an Identity provider. Workspace ONE access also acts as a broker to other identity stores and providers—including Active Directory (AD), Active Directory Federation Services (ADFS), Azure AD, Okta and Ping Identity to enable authentication across on-premises, software-as-a-service (SaaS), web and native applications. Available as a cloud-hosted service, Workspace ONE Access is an integral part of the Workspace ONE platform.
|
||||
|
||||
Refer to our detailed guide on [how to configure supervisor with Workspace ONE Access]({{< ref "docs/howto/idps/configure-supervisor-with-workspace_one_access.md" >}}).
|
||||
Refer to our detailed guide on [how to configure supervisor with Workspace ONE Access]({{< ref "docs/howto/supervisor/configure-supervisor-with-workspace_one_access.md" >}}).
|
||||
|
||||
## What else is in this release?
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user