<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Security on Spinnaker</title>
		<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/other_config/security/</link>
		<description>Recent content in Security on Spinnaker</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/other_config/security/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Administrator functionality</title>
				<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/other_config/security/admin/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/other_config/security/admin/</guid>
				<description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;In Spinnaker, it is possible to define that users belonging to a certain role are considered &amp;ldquo;Administrators&amp;rdquo;. This&#xA;virtually removes all READ/WRITE restrictions to accounts and applications for these users.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;This feature gives admins an immense amount of power. Proceed with caution.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;h2 id=&#34;enable-and-configure-admin-functionality&#34;&gt;Enable and Configure Admin functionality&lt;/h2&gt;&#xA;&lt;h3 id=&#34;manually-add-configuration-in-fiat&#34;&gt;Manually add configuration in Fiat&lt;/h3&gt;&#xA;&lt;p&gt;In the &lt;code&gt;fiat-local.yml&lt;/code&gt; config file, add the following:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-yaml&#34; data-lang=&#34;yaml&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#204a87;font-weight:bold&#34;&gt;fiat&lt;/span&gt;&lt;span style=&#34;color:#000;font-weight:bold&#34;&gt;:&lt;/span&gt;&lt;span style=&#34;color:#f8f8f8&#34;&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f8f8f8&#34;&gt;  &lt;/span&gt;&lt;span style=&#34;color:#204a87;font-weight:bold&#34;&gt;admin&lt;/span&gt;&lt;span style=&#34;color:#000;font-weight:bold&#34;&gt;:&lt;/span&gt;&lt;span style=&#34;color:#f8f8f8&#34;&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f8f8f8&#34;&gt;    &lt;/span&gt;&lt;span style=&#34;color:#204a87;font-weight:bold&#34;&gt;roles&lt;/span&gt;&lt;span style=&#34;color:#000;font-weight:bold&#34;&gt;:&lt;/span&gt;&lt;span style=&#34;color:#f8f8f8&#34;&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#f8f8f8&#34;&gt;      &lt;/span&gt;- &lt;span style=&#34;color:#000&#34;&gt;devops-admin&lt;/span&gt;&lt;span style=&#34;color:#f8f8f8&#34;&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
			</item>
			<item>
				<title>SSL</title>
				<link>https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/other_config/security/ssl/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://deploy-preview-637--spinnaker-io.netlify.app/docs/setup/other_config/security/ssl/</guid>
				<description>&lt;p&gt;This section covers communication with Spinnaker from parties external to your&#xA;Spinnaker instance. That is, any requests between&amp;hellip;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;your browser and the Spinnaker UI (Deck)&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Deck and Gate (the API gateway)&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;any other client and Gate&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;network-configurations&#34;&gt;Network configurations&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Warning&lt;/strong&gt;: Many operators like to get authentication working before adding&#xA;HTTPS, but experience bears out that the transition is not smooth. We recommend&#xA;you implement at least a temporary SSL solution &lt;strong&gt;first&lt;/strong&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
