Setup
Once you clone this repo you will need the following pieces of information added to your .env.local file and they can be found in your Azure AD B2C setup.
- Your application id
- Your Resource Name
- Your B2C Flow Name
- A Full Scope Value
After you have the above information you will need to save it into a .env.local file at the root of the project. It should look like the example below.
VUE_APP_CLIENT_ID='APPGUIDHERE' VUE_APP_AUTHORITY='https://login.microsoftonline.com/tfp/RESOURCENAMEHERE/FLOWNAMEHERE' VUE_APP_SCOPE_READ='FULLSCOPEVALUEHERE'
Once you have created an application in Azure AD B2C you can the above information in the following locations
You can find your application id under the 'Applications' section.
You can find the Resource Name under the overview section of Azure AD B2C
The B2C Flow name can be found under the 'User Flows (Policies') section. If you don't have one you may need to create one.
Your application will need a scope when obtaining a token and when this example was created this scope needed to be created manually in the application section of the Azure AD B2C app. First select your application from the application section of Azure AD B2C then select the 'Published Scopes' section. I had to create a user.read scope for this example. You will want to capture the Full Scope Value field of this scope for user later.
Once this scope is created you will need to give you app access to it from the 'API access' section by using the 'Add' button.
