<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Oidc on Alwaldend</title>
		<link>https://alwaldend.com/tags/oidc/</link>
		<description>Recent content in Oidc on Alwaldend</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="https://alwaldend.com/tags/oidc/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Harbor login</title>
				<link>https://alwaldend.com/docs/tools/vault/harbor_login/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://alwaldend.com/docs/tools/vault/harbor_login/</guid>
				<description>&lt;p&gt;The plugin destroys its Harbor session on normal shutdown and checks that the&#xA;original session ID is rejected by the current-user API. Cleanup uses Harbor&amp;rsquo;s&#xA;&lt;code&gt;/c/oidc/logout&lt;/code&gt; endpoint (available in newer Harbor releases) and does not follow&#xA;the optional identity-provider logout redirect. Unsupported endpoints, network&#xA;failures, or sessions that remain valid are reported as cleanup errors. Session&#xA;expiry remains server-controlled; forced termination cannot guarantee logout.&lt;/p&gt;&#xA;&lt;p&gt;The session destruction behavior is defined by Harbor&amp;rsquo;s&#xA;&lt;a href=&#34;https://github.com/goharbor/harbor/blob/main/src/core/controllers/oidc.go&#34;&gt;OIDC controller&lt;/a&gt;.&#xA;Vault tokens created by the invocation are revoked after session cleanup.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Vault OIDC provider</title>
				<link>https://alwaldend.com/docs/projects/tf_modules/vault_oidc_provider/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://alwaldend.com/docs/projects/tf_modules/vault_oidc_provider/</guid>
				<description></description>
			</item>
	</channel>
</rss>
