<p>20 April 2021, 14:00 - 14:55</p>

<p>Present: Mattias, Balazs, David, Aleksandr, Maiken, Anders (from 14:45),&nbsp;Oxana</p>

<p>== News</p>

<ul>
	<li>REST interface is being tested with ACT, so far looks OK with the test site; involves data staging. Some adjustments in the aCT are needed, as path to the session directory and control files have changed. All is well documented.</li>
	<li>News from GDB: Site-BDII is not needed by WLCG, but EGI still needs it, and there are 188 ARC-CEs in EGI now (and 22 CREM CEs, 108 HTCondor-CEs);&nbsp;Hashicorp's vault looks like a good soluton for browserless token handling;&nbsp;future baseline&nbsp;Linux OS is still undecided.</li>
	<li>The "WLCG Tokens for CEs" hackathon is planned for June 3/4, we must attend.</li>
	<li>There's a wish to quantify ARC scalability, something to be better defined. Job rate (for different kinds of jobs, probably not single-core ones) can be a metric. Many things depend on hardware and underlying OS/FS. Number of jobs might not vene be a good metric for multicore jobs, so other metrics need to be considered.&nbsp;May 4 time slot will be dedicated to the ARC scalability mini-workshop (invite NT1, IJS)&nbsp;</li>
	<li>New APEL protocol testing: it is possible that for the APEL's REST interface, external dependencies may not even be needed, testing is ongoing.&nbsp;</li>
</ul>

<p>== Status of tokens support</p>

<p>The level of token support in ARC is experimental, pre-production, available since release 6.6. It definitely works with EMI-ES, and should work with REST, though not testded yet. The implemented profile is the one by WLCG-AuthZ-WG, so ARC should be listed as a technology that implements it in the AuthZ-WG github. On the client side, there should be a variable set, containing the token, and then it will be used for authentication. For delegation, X509 will be still used. The client-side variable might have changed, needs to be tested. The configuration template for the authorisation parameter lists attributes that can be used for authorisation. Also X509-style authorisation is possible.</p>

<p><br>
== Release</p>

<p>Nightlies for 6.11 candidate are being tested at 3 sites, also reported to work well at NIKHEF's test site.&nbsp;</p>

<p><br>
== Bugs</p>

<p>Some small progress in bug-fixing, nothing to discuss.</p>