ClaimsTransformation seems to create an extra attribute
I am using a claim transformation, which results in creating an extra attribute in my B2C database with the datatype (odata.type) of the value of the new attribute. What am I doing wrong? Why am i getting the extra attribute?
Here is what I see in B2C Graph for the user:
"extension_0428f3354957491e96bb7ce51b81d46a_TOUAcceptedDateTime@odata.type": "Edm.DateTime",
"extension_0428f3354957491e96bb7ce51b81d46a_TOUAcceptedDateTime": "2019-01-18T21:43:36.3993383Z"
This is how the transformation is used in the profile which writes the new attribute out (it is not used anywhere else):
<InputClaimsTransformations>
<InputClaimsTransformation ReferenceId="GetConsentDateTime" />
</InputClaimsTransformations>
Defined as:
<ClaimsTransformation Id="GetConsentDateTime" TransformationMethod="GetCurrentDateTime">
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="extension_TOUAcceptedDateTime" TransformationClaimType="currentDateTime" />
</OutputClaims>
</ClaimsTransformation>
azure-ad-b2c
asked Jan 18 at 21:55
MarcMarc
385
add a comment |
I am using a claim transformation, which results in creating an extra attribute in my B2C database with the datatype (odata.type) of the value of the new attribute. What am I doing wrong? Why am i getting the extra attribute?
Here is what I see in B2C Graph for the user:
"extension_0428f3354957491e96bb7ce51b81d46a_TOUAcceptedDateTime@odata.type": "Edm.DateTime",
"extension_0428f3354957491e96bb7ce51b81d46a_TOUAcceptedDateTime": "2019-01-18T21:43:36.3993383Z"
This is how the transformation is used in the profile which writes the new attribute out (it is not used anywhere else):
<InputClaimsTransformations>
<InputClaimsTransformation ReferenceId="GetConsentDateTime" />
</InputClaimsTransformations>
Defined as:
<ClaimsTransformation Id="GetConsentDateTime" TransformationMethod="GetCurrentDateTime">
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="extension_TOUAcceptedDateTime" TransformationClaimType="currentDateTime" />
</OutputClaims>
</ClaimsTransformation>
azure-ad-b2c
asked Jan 18 at 21:55
MarcMarc
385
add a comment |
I am using a claim transformation, which results in creating an extra attribute in my B2C database with the datatype (odata.type) of the value of the new attribute. What am I doing wrong? Why am i getting the extra attribute?
Here is what I see in B2C Graph for the user:
"extension_0428f3354957491e96bb7ce51b81d46a_TOUAcceptedDateTime@odata.type": "Edm.DateTime",
"extension_0428f3354957491e96bb7ce51b81d46a_TOUAcceptedDateTime": "2019-01-18T21:43:36.3993383Z"
This is how the transformation is used in the profile which writes the new attribute out (it is not used anywhere else):
<InputClaimsTransformations>
<InputClaimsTransformation ReferenceId="GetConsentDateTime" />
</InputClaimsTransformations>
Defined as:
<ClaimsTransformation Id="GetConsentDateTime" TransformationMethod="GetCurrentDateTime">
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="extension_TOUAcceptedDateTime" TransformationClaimType="currentDateTime" />
</OutputClaims>
</ClaimsTransformation>
azure-ad-b2c
asked Jan 18 at 21:55
MarcMarc
385
I am using a claim transformation, which results in creating an extra attribute in my B2C database with the datatype (odata.type) of the value of the new attribute. What am I doing wrong? Why am i getting the extra attribute?
Here is what I see in B2C Graph for the user:
"extension_0428f3354957491e96bb7ce51b81d46a_TOUAcceptedDateTime@odata.type": "Edm.DateTime",
"extension_0428f3354957491e96bb7ce51b81d46a_TOUAcceptedDateTime": "2019-01-18T21:43:36.3993383Z"
This is how the transformation is used in the profile which writes the new attribute out (it is not used anywhere else):
<InputClaimsTransformations>
<InputClaimsTransformation ReferenceId="GetConsentDateTime" />
</InputClaimsTransformations>
Defined as:
<ClaimsTransformation Id="GetConsentDateTime" TransformationMethod="GetCurrentDateTime">
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="extension_TOUAcceptedDateTime" TransformationClaimType="currentDateTime" />
</OutputClaims>
</ClaimsTransformation>
azure-ad-b2c
azure-ad-b2c
asked Jan 18 at 21:55
MarcMarc
385
asked Jan 18 at 21:55
MarcMarc
385
asked Jan 18 at 21:55
MarcMarc
385
asked Jan 18 at 21:55
MarcMarc
385
asked Jan 18 at 21:55
MarcMarc
385
385
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You aren't doing anything wrong.
For a DateTime attribute, Azure AD B2C reads and writes:
- The attribute value as the string representation of the date-time value.
- An "metadata" value that specifies the attribute type.
The "metadata" value helps with serialization of the attribute value.
answered Jan 21 at 1:35
Chris PadgettChris Padgett
6,040139
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54261933%2fclaimstransformation-seems-to-create-an-extra-attribute%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You aren't doing anything wrong.
For a DateTime attribute, Azure AD B2C reads and writes:
- The attribute value as the string representation of the date-time value.
- An "metadata" value that specifies the attribute type.
The "metadata" value helps with serialization of the attribute value.
answered Jan 21 at 1:35
Chris PadgettChris Padgett
6,040139
add a comment |
You aren't doing anything wrong.
For a DateTime attribute, Azure AD B2C reads and writes:
- The attribute value as the string representation of the date-time value.
- An "metadata" value that specifies the attribute type.
The "metadata" value helps with serialization of the attribute value.
answered Jan 21 at 1:35
Chris PadgettChris Padgett
6,040139
add a comment |
You aren't doing anything wrong.
For a DateTime attribute, Azure AD B2C reads and writes:
- The attribute value as the string representation of the date-time value.
- An "metadata" value that specifies the attribute type.
The "metadata" value helps with serialization of the attribute value.
answered Jan 21 at 1:35
Chris PadgettChris Padgett
6,040139
You aren't doing anything wrong.
For a DateTime attribute, Azure AD B2C reads and writes:
- The attribute value as the string representation of the date-time value.
- An "metadata" value that specifies the attribute type.
The "metadata" value helps with serialization of the attribute value.
answered Jan 21 at 1:35
Chris PadgettChris Padgett
6,040139
answered Jan 21 at 1:35
Chris PadgettChris Padgett
6,040139
answered Jan 21 at 1:35
Chris PadgettChris Padgett
6,040139
answered Jan 21 at 1:35
Chris PadgettChris Padgett
6,040139
6,040139
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54261933%2fclaimstransformation-seems-to-create-an-extra-attribute%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
