<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resources on MCP Toolbox for Databases</title><link>/resources/</link><description>Recent content in Resources on MCP Toolbox for Databases</description><generator>Hugo</generator><language>en</language><atom:link href="/resources/index.xml" rel="self" type="application/rss+xml"/><item><title>Generic OIDC Auth</title><link>/resources/authservices/generic/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/resources/authservices/generic/</guid><description>&lt;h2 id="getting-started">Getting Started&lt;/h2>
&lt;p>The Generic Auth Service allows you to integrate with any OpenID Connect (OIDC)
compliant identity provider (IDP). It discovers the JWKS (JSON Web Key Set) URL
either through the provider&amp;rsquo;s &lt;code>/.well-known/openid-configuration&lt;/code> endpoint or
directly via the provided &lt;code>authorizationServer&lt;/code>.&lt;/p>
&lt;p>To configure this auth service, you need to provide the &lt;code>audience&lt;/code> (typically
your client ID or the intended audience for the token), the
&lt;code>authorizationServer&lt;/code> of your identity provider, and optionally a list of
&lt;code>scopesRequired&lt;/code> that must be present in the token&amp;rsquo;s claims.&lt;/p></description></item></channel></rss>