<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Ok,</p>
<p>Thank you for the clarification.</p>
<p>So for now, there no case where it would work as intended, i
guess.</p>
<p>Even if it doesn't work, though, can you give some examples of
the step names that were meant to be used inside these
"resolutionPhases" parameters?</p>
<p>And although, is that the resolutionPhases filtering of data
connectors which doesn't work ? Or the whole
activationConditionRef mechanism for Data Connectors? Which would
mean that excludeRelyingParties would not work either?</p>
<pre class="moz-signature" cols="72">Pierre Sagne.
</pre>
<div class="moz-cite-prefix">Le 04/10/2024 à 14:40, Cantor, Scott a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:43174DCC-B825-48AE-89CB-36B7AFC3AD69@osu.edu">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator"
content="Microsoft Word 15 (filtered medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;
mso-ligatures:none;}.MsoChpDefault
{mso-style-type:export-only;}div.WordSection1
{page:WordSection1;}</style>
<div class="WordSection1">
<p class="MsoPlainText">> I'm trying to figure what I should
pass to the<o:p></o:p></p>
<p class="MsoPlainText">> resolutionPhases or
excludeResolutionPhases parameter to<o:p></o:p></p>
<p class="MsoPlainText">> achieve this.<o:p></o:p></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:black">This feature
doesn't really work right because of some bugs and
complexity due to the information needed to actually locate
the information at runtime to enforce it.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:black">It only works
for now if the AttributeResolutionContext is created in the
place the IdP puts it, but oftentimes “special” cases need
to stick it elsewhere to avoid collisions, and that breaks
it right now. 5.2 should fix that limitation.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:black">If you wanted
to use it for your MFA flow, then you’d have to make sure
to create the resolution context directly under the PRC (and
of course remove it to clean up) and you could set it to
whatever you wanted really, and that would work ok to depend
on it in your resolution and to exclude it in the IdP’s
standard ones.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:black">I'm not likely
to go in and adjust it all and define consistent rules for
the labels until a major version change to V6 because of the
potential to disrupt people’s systems. At that point I’ll
get it defined every time we run the service and define the
values used internally, which will typically be flow IDs,
yes. I would probably use the fully qualified ones.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="color:black">I realize it’s
a nice feature, and I’d like to fix it sooner, but I think
stability of upgrades has to trump anything else.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText">-- Scott<o:p></o:p></p>
<p class="MsoPlainText"><span style="color:black"><o:p> </o:p></span></p>
</div>
</blockquote>
</body>
</html>