<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Custom Identity Providers on</title><link>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/administration/custom-idps/</link><description>Recent content in Custom Identity Providers on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Thu, 13 Apr 2023 08:49:15 +0000</lastBuildDate><atom:link href="https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/administration/custom-idps/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Custom Identity Providers to Authenticate to Chainguard</title><link>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/administration/custom-idps/custom-idps/</link><pubDate>Mon, 17 Apr 2023 08:48:45 +0000</pubDate><guid>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/administration/custom-idps/custom-idps/</guid><description>The Chainguard platform supports Single Sign-on (SSO) authentication for users. By default, users can log in with GitHub, GitLab, and Google, but SSO support allows users to bring their own identity provider for authentication. This is helpful when your organization mandates using a corporate identity provider — like Okta or Azure Active Directory — to authenticate to SaaS products.
Usage Once an administrator has configured an identity provider and set up their organization, users can authenticate at the command line and in the web console using the identity provider’s organization.</description></item></channel></rss>