[java-idp-oidc] branch main updated: Fix sub example definitions, should be Scoped.

[Scott Cantor]

This is an automated email from the git hooks/post-receive script.

scantor pushed a commit to branch main
in repository java-idp-oidc.

View the commit online:
http://git.shibboleth.net/view/?p=java-idp-oidc.git;a=commit;h=9cb136cbfa696c4f2486e3c0a18a3ff1994962c3

The following commit(s) were added to refs/heads/main by this push:
       new  9cb136cb  Fix sub example definitions, should be Scoped.
9cb136cb is described below

commit 9cb136cbfa696c4f2486e3c0a18a3ff1994962c3
Author: Scott Cantor <cantor.2 at osu.edu>
AuthorDate: Fri Jan 15 09:45:04 2021 -0500

    Fix sub example definitions, should be Scoped.
---
 .../idp/plugin/oidc/op/conf/oidc-attribute-resolver.xml          | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/idp-oidc-extension-impl/src/main/resources/net/shibboleth/idp/plugin/oidc/op/conf/oidc-attribute-resolver.xml b/idp-oidc-extension-impl/src/main/resources/net/shibboleth/idp/plugin/oidc/op/conf/oidc-attribute-resolver.xml
index ecf103a9..4d9f3c64 100644
--- a/idp-oidc-extension-impl/src/main/resources/net/shibboleth/idp/plugin/oidc/op/conf/oidc-attribute-resolver.xml
+++ b/idp-oidc-extension-impl/src/main/resources/net/shibboleth/idp/plugin/oidc/op/conf/oidc-attribute-resolver.xml
@@ -13,7 +13,8 @@
     This example (the data connector in particular) will generate public or pairwise values depending on client registration.
     The public values will depend on, but not expose, an underlying managed value.
     -->
-    <AttributeDefinition id="subject" xsi:type="Simple" activationConditionRef="shibboleth.oidc.Conditions.SubjectRequired">
+    <AttributeDefinition id="subject" xsi:type="Scoped" scope="%{idp.scope}"
+            activationConditionRef="shibboleth.oidc.Conditions.SubjectRequired">
         <InputDataConnector ref="computedSubjectId" attributeNames="subjectId"/>
         <AttributeEncoder xsi:type="oidcext:OIDCScopedString" name="sub" />
     </AttributeDefinition>
@@ -22,12 +23,14 @@
     These examples use activation conditions and filter rules elsewhere to allow for different formats for public and pairwise.
     -->
     <!--
-    <AttributeDefinition id="subject-public" xsi:type="Simple" activationConditionRef="shibboleth.oidc.Conditions.PublicRequired">
+    <AttributeDefinition id="subject-public" xsi:type="Scoped" scope="%{idp.scope}"
+            activationConditionRef="shibboleth.oidc.Conditions.PublicRequired">
         <InputAttributeDefinition ref="uid" />
         <AttributeEncoder xsi:type="oidcext:OIDCScopedString" name="sub" />
     </AttributeDefinition>
 
-    <AttributeDefinition id="subject-pairwise" xsi:type="Simple" activationConditionRef="shibboleth.oidc.Conditions.PairwiseRequired">
+    <AttributeDefinition id="subject-pairwise" xsi:type="Scoped" scope="%{idp.scope}"
+            activationConditionRef="shibboleth.oidc.Conditions.PairwiseRequired">
         <InputDataConnector ref="computedSubjectId" attributeNames="subjectId"/>
         <AttributeEncoder xsi:type="oidcext:OIDCScopedString" name="sub" />
     </AttributeDefinition>

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.