feat!: bypass superpin environment settings #8
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.
BREAKING CHANGE
This PR introduces the ability to bypass certain environment restrictions.
Use case
There are situations where you may need to provide a third party with access to your system, such as when Apple’s app store review team requires a username and password to log in. Previously, logging in with a superpin in a production environment was not possible because the user wouldn’t receive an email notification.
This PR enhances the security of the package in two key ways:
Migration
config('totp-login.superpin')
toconfig('totp-login.superpin.pin')
.totp-login.superpin.*
config entries. The staging system is not allowed to use the superpin by default.