<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Joel,<br>
<br>
Yes, all you need to do is define a unique entityID for that application.<br>
<br>
Then, add a relying party override by name. In that override, define a reference to "attribute-release" on the SAML 2 configuration as a post authentication flow.<br>
<br>
<a class="moz-txt-link-freetext" href="https://wiki.shibboleth.net/confluence/display/IDP30/ConsentConfiguration">https://wiki.shibboleth.net/confluence/display/IDP30/ConsentConfiguration</a><br>
<br>
Let me know if you need a more detailed example,<br>
Nate.<br>
<br>
On 01/26/2017 01:08 AM, Joel Levin wrote:<br>
</div>
<blockquote cite="mid:CAGfxv+8dD5x5Zuip6sFNLHgd6c3poffGYFMOC523zFKwbhaMyw@mail.gmail.com" type="cite">
<div dir="ltr">
<div>
<div>Is there a way to explicitly specify application whereby the attribute-consent will appear?<br>
<br>
</div>
We do not need it for 95% of applications -- but require for 5% or so.<br>
<br>
</div>
j.<br>
<div>
<div>
<div><br>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>