<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.EmailStyle17
{font-family:"Calibri",sans-serif;
color:windowtext}
.MsoChpDefault
{font-family:"Calibri",sans-serif}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
div.WordSection1
{}
ol
{margin-bottom:0cm}
ul
{margin-bottom:0cm}
-->
</style>
</head>
<body lang="EN-IN" link="#0563C1" vlink="#954F72">
Why not have lbaas do step 2? Even better would be to help with the instance user spec and combined with lbaas doing step 2, you could restrict secret access to just the amphora that need the secret?<br>
<br>
Thanks,<br>
Kevin <strong>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</strong>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> Vijay Venkatachalam<br>
<b>Sent:</b> Tuesday, September 15, 2015 7:06:39 PM<br>
<b>To:</b> OpenStack Development Mailing List (openstack-dev@lists.openstack.org)<br>
<b>Subject:</b> [openstack-dev] [Barbican] Providing service user read access to all tenant's certificates<br>
</font><br>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal">Hi,</p>
<p class="MsoNormal"> Is there a way to provide read access to a certain user to all secrets/containers of all project/tenant’s certificates?</p>
<p class="MsoNormal"> This user with universal “read” privilege’s will be used as a service user by LBaaS plugin to read tenant’s certificates during LB configuration implementation.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> Today’s LBaaS users are following the below mentioned process
</p>
<p class="MsoListParagraph" style="margin-left:72.0pt; text-indent:-18.0pt"><span style="">1.<span style="font:7.0pt "Times New Roman"">
</span></span>tenant’s creator/admin user uploads a certificate info as secrets and container</p>
<p class="MsoListParagraph" style="margin-left:72.0pt; text-indent:-18.0pt"><span style="">2.<span style="font:7.0pt "Times New Roman"">
</span></span>User then have to create ACLs for the LBaaS service user to access the containers and secrets</p>
<p class="MsoListParagraph" style="margin-left:72.0pt; text-indent:-18.0pt"><span style="">3.<span style="font:7.0pt "Times New Roman"">
</span></span>User creates LB config with the container reference</p>
<p class="MsoListParagraph" style="margin-left:72.0pt; text-indent:-18.0pt"><span style="">4.<span style="font:7.0pt "Times New Roman"">
</span></span>LBaaS plugin using the service user will then access container reference provided in LB config and proceeds to implement.</p>
<p class="MsoNormal" style="margin-left:36.0pt"> </p>
<p class="MsoNormal" style="margin-left:36.0pt">Ideally we would want to avoid step 2 in the process. Instead add a step 5 where the lbaas plugin’s service user checks if the user configuring the LB has read access to the container reference provided.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks,</p>
<p class="MsoNormal">Vijay V.</p>
</div>
</div>
</body>
</html>