Files
edx-platform/openedx/core/djangoapps/user_api
Manjinder Singh cea795b02e Added new auth class (#23018)
* Added new auth class

- Created new class called OAuth2AuthenticationAllowInactiveUser, which replaces old class with same name
- Renames previous  OAuth2AuthenticationAllowInactiveUser to  OAuth2AuthenticationAllowInactiveUserDeprecated
- Replaced all imports of  OAuth2AuthenticationAllowInactiveUser to call deprecated class instead
- testing new class in discussion(added flag based on django setting)
2020-02-06 10:37:27 -05:00
..
2020-02-06 10:37:27 -05:00
2019-12-30 10:35:30 -05:00
2019-12-30 12:25:38 -05:00
2019-12-30 10:35:30 -05:00
2020-02-06 10:37:27 -05:00
2019-12-30 10:35:30 -05:00
2019-12-30 10:35:30 -05:00
2019-12-30 12:25:38 -05:00
2019-12-30 12:25:38 -05:00
2020-01-30 16:36:02 +05:00
2019-12-30 10:35:30 -05:00
2019-12-30 10:35:30 -05:00
2019-12-30 10:35:30 -05:00
2019-12-30 10:35:30 -05:00
2019-12-30 12:25:38 -05:00
2019-12-30 12:25:38 -05:00

Status: Active

Responsibilities
================
The user_api app is currently a catch all that is used to provide various apis that are related to the user and also to features within the platform.

Intended responsibility: To manage user profile and general account information and to provide APIs to do so easily. This includes the following features: user preference, user profile, user retirement, and account activation/deactivation.

Direction: Decompose
===============
Currently this app is a catch all for many user related information even when that information should really belong in a different app.  If you are building a feature and need to provide information about a user within the context of your feature, you should localize that API to your feature and make your assumptions about what user information you need clear.

For example authentication related APIs have already been moved to the user_authn django app.

Glossary
========

More Documentation
==================