- 500 error occurs when a non-admin user attempts to add an invalid
credential during schedule creation
- This change checks that the user can add the object to
serializer.validated_data, instead of serializer.initial_data
- The invalid credential field is purged in .validated_data, so the
request passes through cleanly
- Fix for awx issue #4147
Oauth2 settings were initialized early in the awx import stage, and
those settings were not modifiable. This change allows oauth2 to check
for settings in django.conf settings, which are dynamically updated
through api calls at runtime. As a result, oauth2 settings will match
the values in django.conf settings at any point in time.
Grab AUTHORIZATION_CODE_EXPIRE_SECONDS from oauth2_settings
rather than hard code.
Add REFRESH_TOKEN_EXPIRE_SECONDS to valid_key_names
in OAuth2ProviderField class
- Set OAUTH2 REFRESH_TOKEN_EXPIRE_SECONDS to 1 month
(2628000 seconds)
- If not set, awx-manage cleartokens, or cleanup_tokens,
will not work properly
- Once cleartokens is run, this setting is the amount of
time after an access token expires that we keep its
refresh token in the database
- Check that model User object exists with id=user_id
before attempting to save to database
- UserSessionMembership saves to the database using
foreign key, User
- However, User with matching id might not exist if
browser sends request with stale cookies
- Change made in regards to issue #4334
- Bug: API error if LDAPServerURIField contains a number in the top level domain
- Add custom regex in LDAPServerURIField class that is passed to django
URLValidator
- The custom regex allows for numbers to be present in the top level domain
- Unit tests check that valid URIs pass through URLValidator, and that
invalid URIs raise the correct exception
- Related to issue #3646
Seth Foster