Jas Suri
Jas Suri
I found more recently that leaving GOG open for some time after restart, it fixes itself. No idea what the reason is. I suspect it’s a GOG bug.
Need this so bad.
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)
Best to use the automated tool to setup the starter pack [here](https://aka.ms/iefsetup).
This is better posted on stackoverflow, as this is a config issue with your API call. Either you have incorrect api key or incorrectly formed json body.
I don’t see an issue with the content defs. That error would not trigger on the action of sending otp code. Your other error of bad request from api call...
Is this different from `samples/policies/passwordless-email`?
> The problem I am experiencing though is I cant seem to get PhoneFactor-InputOrVerify to execute in this scenario. What is the observation? Did you check the preconditions? I wouldn’t...
The solution would be to add SM-AAD as session management to the offending technical profile which re prompts for TOU on SSO scenarios. I shall update the sample.
I did apply a fix: https://github.com/azure-ad-b2c/samples/commit/f2824296696c42e207840a6c11733fa0dc20a033 Can you provide more details on the behavior?