AzureIDIR (IDIR MFA) support#250
Merged
Merged
Conversation
3a014b4 to
49bb68c
Compare
Already enabled on local environment, but crucially, the corresponding idir/azureidir user is now treated as the same user (instead of completely different ones).
49bb68c to
f631072
Compare
TimCsaky
approved these changes
Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces full support for IDIR MFA (a.k.a.
azureidir) as an identity provider, alongside the existing SiteMinder IDIR (oridir).Partial support was already available in the local dev environment, but behaviour was buggy. Some examples of this include:
idiruser didn't carry over to theazureidir-equivalent userSimilar to the COMS-side changes made to enable IDIR MFA (bcgov/common-object-management-service#320), this was achieved by 'coercing'
authStore.profile.identity_providertoidirwheneverazureidirwas present in the corresponding JWT field.https://apps.nrs.gov.bc.ca/int/jira/browse/SHOWCASE-3713
Types of changes
New feature (non-breaking change which adds functionality)
Checklist
Further comments
See also: bcgov/common-object-management-service#320