#e2e test for @bifravst on
@Azure are getting somewhere ... however every day
brings new hurdles. Today I discovered that I can't programmatically
authenticate users against Azure AD B2C using the same function app, because it
can only have one Issuer Url configured for auth.
Embedded Photo

Wed, 05 Aug 2020 16:30:56 UTC

1 reply

Replying to @coderbyheart

So this is fine for CI #e2e test, but you it means you can't easily run these
test against a development instance. :/

Also, the Issuer URL has a different value for developer generated tokens. Which
means a different config in prod vs. test. 🤕