16.0 mig auth sms #1
Draft
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
Currently translated at 100.0% (18 of 18 strings) Translation: server-auth-16.0/server-auth-16.0-auth_api_key Translate-URL: https://translation.odoo-community.org/projects/server-auth-16-0/server-auth-16-0-auth_api_key/it/
To show the button up, it is requiring a getter that is not defined on vault field. So the getter is added and make the button works correctly. Steps to reproduce the problem: 1. Go to Vault 2. Enter/Create a Vault 3. Press on entries 4. Access/Create a entry with a field The button with external link is not showed
Co-authored-by: Kévin Roche <[email protected]>
Currently translated at 100.0% (26 of 26 strings) Translation: server-auth-16.0/server-auth-16.0-impersonate_login Translate-URL: https://translation.odoo-community.org/projects/server-auth-16-0/server-auth-16-0-impersonate_login/it/
…ssword_write_date value. It happens that when you install the module, all the users that previously existed before that won't have a value set for the new field password_write_date. And when the validation of minimal hours has passed between the last password write date and now is done, it gets an error of unsupported operands between a bool and timedelta. With this change, it won't be necessary to validate the last password date if it's the first time reseting password, and when the password is changed it will correctly save the value on password_write_date and will be working normally afterwards.
…g users that don't have it. This fixes the password expiration date and other validations that require an existing value for password update date. [IMP] password_security: Simplify validation on password reset.
…g users that don't have it. This fixes the password expiration date and other validations that require an existing value for password update date. [IMP] password_security: Simplify validation on password reset.
The group mapping in query mode fails if LDAP returns binary data in any of the fields. This adds a function that handles such situation by base64 encoding it. The new test test_users_ldap_groups_ldap_returns_binary_data covers the common case where LDAP return binary data in thumbnailPhoto.
Currently translated at 100.0% (18 of 18 strings) Translation: server-auth-16.0/server-auth-16.0-auth_oauth_ropc Translate-URL: https://translation.odoo-community.org/projects/server-auth-16-0/server-auth-16-0-auth_oauth_ropc/it/
NL66278
force-pushed
the
16.0-mig-auth_sms
branch
5 times, most recently
from
366a4af to
c1b5cd3
Compare
NL66278
force-pushed
the
16.0-mig-auth_sms
branch
from
c1b5cd3 to
4b09219
Compare
Also take care of compatibility with auth_oauth.
thomaspaulb
force-pushed
the
16.0-mig-auth_sms
branch
from
9aa4f28 to
cdfcc8f
Compare
…assword reset flow intact
NL66278
force-pushed
the
16.0-mig-auth_sms
branch
from
cf4ed4f to
317fe99
Compare
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.
No description provided.