Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Having trouble following RP-SAML walkthrough #41

Open
madelson opened this issue Dec 19, 2018 · 1 comment
Open

Having trouble following RP-SAML walkthrough #41

madelson opened this issue Dec 19, 2018 · 1 comment

Comments

@madelson
Copy link

madelson commented Dec 19, 2018

Hello,

I've been trying to follow https://github.com/Azure-Samples/active-directory-b2c-advanced-policies/blob/master/Walkthroughs/RP-SAML.md after having completed the instructions on https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-get-started-custom.

Having gone through it, I have yet to get things working. Here are some of the issues/discrepancies I've run into after following both tutorials:

  • In step 3 of “create the SAML token issuer”, it has you setting up the technical profile for Saml2AssertionIssuer. There, it makes no reference to changing the StorageReferenceIds for the crypto keys. However, towards the bottom, it has an example profile with these filled in with the auto-generated name prefixes. Which is right?
  • In step 2 of “add the saml relaying party to user journey(s)”, it asks you to find the UserJourney with Id=”SignIn”. I only had “SignUpOrSignIn”, so I used that, is that OK?
  • Similarly, in step 6, it tells you to copy the SignIn.xml file, but I only had SignUpOrSignin.xml so I used that. Is that OK?
  • Same section, step 8, it says to “modify its policy ID to new GUID”. My policy ID was currently “B2C_1A_signup_signin”. Should it be “B2C_1A_signup_signin_saml” or truly a GUID?
  • Relatedly, there is also a PublicPolicyUri="http://thetenantimusing.onmicrosoft.com/B2C_1A_signup_signin. Does this need to change?
@JasSuri
Copy link

JasSuri commented Jan 10, 2019

Hi

  1. The prefixes are required (B2C_1A_xxxxxx).

  2. That is ok

  3. Also ok

  4. “B2C_1A_signup_signin_saml” is fine, shouldn't be a GUID.

  5. Yes update to match 4)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants