Add support for Auth Scheme customization on build time #8261
Conversation
This file contains 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.
Summary
The authentication schemes were hardcoded to use
mmauthbetafor our Beta app andmmauthfor our release app. While the server allows this schemes to be changed in order to be used with custom mobile builds, the mobile app did not have a way to easily customize them, having to make some changes in the code before compiling.This PR introduces a couple of environment variables to be able to change these authentication schemes on build time.
Note: This is backwards compatible so that the app builds the same way as before if no env var is set.
Ticket Link
N/A.
Release Note