Azure B2C disable Sign up of a SignUpAndSignIn policy
I need some advice on Customising Azure B2C.
I've been looking at both portal based customisation and the Identity Experience Framework.
My key requirement is to have full control of the look and feel of the login experience. However, users must not be able sign up as this is handled by a separate business process. I understand that I cannot use a simple SignIn policy as B2C doesn't provide the required level of customisation.
I'm unable to find any solid documentation that describe how/if this is possible.
I've followed this documentation for the Azure B2C Identity Experience Framework. But can't see where I would be able to disable signup.
https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-get-started-custom
azure azure-ad-b2c asked Nov 14 '18 at 13:00
benemberybenembery
454314
add a comment |
I need some advice on Customising Azure B2C.
I've been looking at both portal based customisation and the Identity Experience Framework.
My key requirement is to have full control of the look and feel of the login experience. However, users must not be able sign up as this is handled by a separate business process. I understand that I cannot use a simple SignIn policy as B2C doesn't provide the required level of customisation.
I'm unable to find any solid documentation that describe how/if this is possible.
I've followed this documentation for the Azure B2C Identity Experience Framework. But can't see where I would be able to disable signup.
https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-get-started-custom
azure azure-ad-b2c asked Nov 14 '18 at 13:00
benemberybenembery
454314
add a comment |
I need some advice on Customising Azure B2C.
I've been looking at both portal based customisation and the Identity Experience Framework.
My key requirement is to have full control of the look and feel of the login experience. However, users must not be able sign up as this is handled by a separate business process. I understand that I cannot use a simple SignIn policy as B2C doesn't provide the required level of customisation.
I'm unable to find any solid documentation that describe how/if this is possible.
I've followed this documentation for the Azure B2C Identity Experience Framework. But can't see where I would be able to disable signup.
https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-get-started-custom
azure azure-ad-b2c asked Nov 14 '18 at 13:00
benemberybenembery
454314
I need some advice on Customising Azure B2C.
I've been looking at both portal based customisation and the Identity Experience Framework.
My key requirement is to have full control of the look and feel of the login experience. However, users must not be able sign up as this is handled by a separate business process. I understand that I cannot use a simple SignIn policy as B2C doesn't provide the required level of customisation.
I'm unable to find any solid documentation that describe how/if this is possible.
I've followed this documentation for the Azure B2C Identity Experience Framework. But can't see where I would be able to disable signup.
https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-get-started-custom
azure azure-ad-b2c azure azure-ad-b2c asked Nov 14 '18 at 13:00
benemberybenembery
454314
asked Nov 14 '18 at 13:00
benemberybenembery
454314
asked Nov 14 '18 at 13:00
benemberybenembery
454314
asked Nov 14 '18 at 13:00
benemberybenembery
454314
asked Nov 14 '18 at 13:00
benemberybenembery
454314
454314
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can disable the sign-up button using the setting.showSignupLink metadata:
<TechnicalProfile Id="SelfAsserted-LocalAccountSignin-Email">
<DisplayName>Local Account Signin</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.SelfAssertedAttributeProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<Metadata>
<Item Key="setting.operatingMode">Email</Item>
<Item Key="setting.showSignupLink">false</Item>
<Item Key="ContentDefinitionReferenceId">api.selfasserted</Item>
</Metadata>
<IncludeInSso>false</IncludeInSso>
<InputClaims>
<InputClaim ClaimTypeReferenceId="signInName" />
</InputClaims>
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="signInName" Required="true" />
<OutputClaim ClaimTypeReferenceId="password" Required="true" />
<OutputClaim ClaimTypeReferenceId="objectId" />
<OutputClaim ClaimTypeReferenceId="authenticationSource" />
</OutputClaims>
<ValidationTechnicalProfiles>
<ValidationTechnicalProfile ReferenceId="login-NonInteractive" />
</ValidationTechnicalProfiles>
<UseTechnicalProfileForSessionManagement ReferenceId="SM-AAD" />
</TechnicalProfile>
answered Nov 14 '18 at 21:04
Chris PadgettChris Padgett
6,270139
@Chirs Padgett thanks you for your answer. Comparing it with the documentation and starter kit it seems that it is also important to remove the following<Item Key="SignUpTarget">SignUpWithLogonEmailExchange</Item>Could you confirm this is the case? I found the example here
– benembery
Nov 15 '18 at 11:29
Hi @benembery Yes, you can remove theSignUpTargetmetadata, as well. Previously, before thesetting.showSignUpLinkwas added by Microsoft, removingSignUpTargetwas the only method for preventing users from clicking the sign-up link (which is why you the other answer was posted by @spottedmahn).
– Chris Padgett
Nov 15 '18 at 20:50
Thanks very much for the advice.
– benembery
Nov 15 '18 at 21:39
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%2f53300861%2fazure-b2c-disable-sign-up-of-a-signupandsignin-policy%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 can disable the sign-up button using the setting.showSignupLink metadata:
<TechnicalProfile Id="SelfAsserted-LocalAccountSignin-Email">
<DisplayName>Local Account Signin</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.SelfAssertedAttributeProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<Metadata>
<Item Key="setting.operatingMode">Email</Item>
<Item Key="setting.showSignupLink">false</Item>
<Item Key="ContentDefinitionReferenceId">api.selfasserted</Item>
</Metadata>
<IncludeInSso>false</IncludeInSso>
<InputClaims>
<InputClaim ClaimTypeReferenceId="signInName" />
</InputClaims>
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="signInName" Required="true" />
<OutputClaim ClaimTypeReferenceId="password" Required="true" />
<OutputClaim ClaimTypeReferenceId="objectId" />
<OutputClaim ClaimTypeReferenceId="authenticationSource" />
</OutputClaims>
<ValidationTechnicalProfiles>
<ValidationTechnicalProfile ReferenceId="login-NonInteractive" />
</ValidationTechnicalProfiles>
<UseTechnicalProfileForSessionManagement ReferenceId="SM-AAD" />
</TechnicalProfile>
answered Nov 14 '18 at 21:04
Chris PadgettChris Padgett
6,270139
@Chirs Padgett thanks you for your answer. Comparing it with the documentation and starter kit it seems that it is also important to remove the following<Item Key="SignUpTarget">SignUpWithLogonEmailExchange</Item>Could you confirm this is the case? I found the example here
– benembery
Nov 15 '18 at 11:29
Hi @benembery Yes, you can remove theSignUpTargetmetadata, as well. Previously, before thesetting.showSignUpLinkwas added by Microsoft, removingSignUpTargetwas the only method for preventing users from clicking the sign-up link (which is why you the other answer was posted by @spottedmahn).
– Chris Padgett
Nov 15 '18 at 20:50
Thanks very much for the advice.
– benembery
Nov 15 '18 at 21:39
add a comment |
You can disable the sign-up button using the setting.showSignupLink metadata:
<TechnicalProfile Id="SelfAsserted-LocalAccountSignin-Email">
<DisplayName>Local Account Signin</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.SelfAssertedAttributeProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<Metadata>
<Item Key="setting.operatingMode">Email</Item>
<Item Key="setting.showSignupLink">false</Item>
<Item Key="ContentDefinitionReferenceId">api.selfasserted</Item>
</Metadata>
<IncludeInSso>false</IncludeInSso>
<InputClaims>
<InputClaim ClaimTypeReferenceId="signInName" />
</InputClaims>
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="signInName" Required="true" />
<OutputClaim ClaimTypeReferenceId="password" Required="true" />
<OutputClaim ClaimTypeReferenceId="objectId" />
<OutputClaim ClaimTypeReferenceId="authenticationSource" />
</OutputClaims>
<ValidationTechnicalProfiles>
<ValidationTechnicalProfile ReferenceId="login-NonInteractive" />
</ValidationTechnicalProfiles>
<UseTechnicalProfileForSessionManagement ReferenceId="SM-AAD" />
</TechnicalProfile>
answered Nov 14 '18 at 21:04
Chris PadgettChris Padgett
6,270139
@Chirs Padgett thanks you for your answer. Comparing it with the documentation and starter kit it seems that it is also important to remove the following<Item Key="SignUpTarget">SignUpWithLogonEmailExchange</Item>Could you confirm this is the case? I found the example here
– benembery
Nov 15 '18 at 11:29
Hi @benembery Yes, you can remove theSignUpTargetmetadata, as well. Previously, before thesetting.showSignUpLinkwas added by Microsoft, removingSignUpTargetwas the only method for preventing users from clicking the sign-up link (which is why you the other answer was posted by @spottedmahn).
– Chris Padgett
Nov 15 '18 at 20:50
Thanks very much for the advice.
– benembery
Nov 15 '18 at 21:39
add a comment |
You can disable the sign-up button using the setting.showSignupLink metadata:
<TechnicalProfile Id="SelfAsserted-LocalAccountSignin-Email">
<DisplayName>Local Account Signin</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.SelfAssertedAttributeProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<Metadata>
<Item Key="setting.operatingMode">Email</Item>
<Item Key="setting.showSignupLink">false</Item>
<Item Key="ContentDefinitionReferenceId">api.selfasserted</Item>
</Metadata>
<IncludeInSso>false</IncludeInSso>
<InputClaims>
<InputClaim ClaimTypeReferenceId="signInName" />
</InputClaims>
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="signInName" Required="true" />
<OutputClaim ClaimTypeReferenceId="password" Required="true" />
<OutputClaim ClaimTypeReferenceId="objectId" />
<OutputClaim ClaimTypeReferenceId="authenticationSource" />
</OutputClaims>
<ValidationTechnicalProfiles>
<ValidationTechnicalProfile ReferenceId="login-NonInteractive" />
</ValidationTechnicalProfiles>
<UseTechnicalProfileForSessionManagement ReferenceId="SM-AAD" />
</TechnicalProfile>
answered Nov 14 '18 at 21:04
Chris PadgettChris Padgett
6,270139
You can disable the sign-up button using the setting.showSignupLink metadata:
<TechnicalProfile Id="SelfAsserted-LocalAccountSignin-Email">
<DisplayName>Local Account Signin</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.SelfAssertedAttributeProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<Metadata>
<Item Key="setting.operatingMode">Email</Item>
<Item Key="setting.showSignupLink">false</Item>
<Item Key="ContentDefinitionReferenceId">api.selfasserted</Item>
</Metadata>
<IncludeInSso>false</IncludeInSso>
<InputClaims>
<InputClaim ClaimTypeReferenceId="signInName" />
</InputClaims>
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="signInName" Required="true" />
<OutputClaim ClaimTypeReferenceId="password" Required="true" />
<OutputClaim ClaimTypeReferenceId="objectId" />
<OutputClaim ClaimTypeReferenceId="authenticationSource" />
</OutputClaims>
<ValidationTechnicalProfiles>
<ValidationTechnicalProfile ReferenceId="login-NonInteractive" />
</ValidationTechnicalProfiles>
<UseTechnicalProfileForSessionManagement ReferenceId="SM-AAD" />
</TechnicalProfile>
answered Nov 14 '18 at 21:04
Chris PadgettChris Padgett
6,270139
answered Nov 14 '18 at 21:04
Chris PadgettChris Padgett
6,270139
answered Nov 14 '18 at 21:04
Chris PadgettChris Padgett
6,270139
answered Nov 14 '18 at 21:04
Chris PadgettChris Padgett
6,270139
6,270139
@Chirs Padgett thanks you for your answer. Comparing it with the documentation and starter kit it seems that it is also important to remove the following<Item Key="SignUpTarget">SignUpWithLogonEmailExchange</Item>Could you confirm this is the case? I found the example here
– benembery
Nov 15 '18 at 11:29
Hi @benembery Yes, you can remove theSignUpTargetmetadata, as well. Previously, before thesetting.showSignUpLinkwas added by Microsoft, removingSignUpTargetwas the only method for preventing users from clicking the sign-up link (which is why you the other answer was posted by @spottedmahn).
– Chris Padgett
Nov 15 '18 at 20:50
Thanks very much for the advice.
– benembery
Nov 15 '18 at 21:39
add a comment |
@Chirs Padgett thanks you for your answer. Comparing it with the documentation and starter kit it seems that it is also important to remove the following<Item Key="SignUpTarget">SignUpWithLogonEmailExchange</Item>Could you confirm this is the case? I found the example here
– benembery
Nov 15 '18 at 11:29
Hi @benembery Yes, you can remove theSignUpTargetmetadata, as well. Previously, before thesetting.showSignUpLinkwas added by Microsoft, removingSignUpTargetwas the only method for preventing users from clicking the sign-up link (which is why you the other answer was posted by @spottedmahn).
– Chris Padgett
Nov 15 '18 at 20:50
Thanks very much for the advice.
– benembery
Nov 15 '18 at 21:39
@Chirs Padgett thanks you for your answer. Comparing it with the documentation and starter kit it seems that it is also important to remove the following
<Item Key="SignUpTarget">SignUpWithLogonEmailExchange</Item> Could you confirm this is the case? I found the example here– benembery
Nov 15 '18 at 11:29
@Chirs Padgett thanks you for your answer. Comparing it with the documentation and starter kit it seems that it is also important to remove the following
<Item Key="SignUpTarget">SignUpWithLogonEmailExchange</Item> Could you confirm this is the case? I found the example here– benembery
Nov 15 '18 at 11:29
Hi @benembery Yes, you can remove the
SignUpTarget metadata, as well. Previously, before the setting.showSignUpLink was added by Microsoft, removing SignUpTarget was the only method for preventing users from clicking the sign-up link (which is why you the other answer was posted by @spottedmahn).– Chris Padgett
Nov 15 '18 at 20:50
Hi @benembery Yes, you can remove the
SignUpTarget metadata, as well. Previously, before the setting.showSignUpLink was added by Microsoft, removing SignUpTarget was the only method for preventing users from clicking the sign-up link (which is why you the other answer was posted by @spottedmahn).– Chris Padgett
Nov 15 '18 at 20:50
Thanks very much for the advice.
– benembery
Nov 15 '18 at 21:39
Thanks very much for the advice.
– benembery
Nov 15 '18 at 21:39
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%2f53300861%2fazure-b2c-disable-sign-up-of-a-signupandsignin-policy%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
