...
So you want to touch JWTs? may be useful for anyone working on any of these challenges.
Also see details about the potential funded contribution FC-18 here, labelled as
| Status | ||||
|---|---|---|---|---|
|
Easier to use
These changes should make authentication easier to use for engineers.
...
https://github.com/openedx/edx-drf-extensions/issues/333Status colour Green title In FC-18 New implementation ticket for https://github.com/openedx/public-engineering/issues/83
This would simplify authentication and maintenance, but wouldn’t necessarily add functionality.
https://github.com/openedx/edx-drf-extensions/issues/327Status colour Green title In FC-18 Related: For some of the past removal work, the new api client wasn’t used, and instead a straight requests object was used and worked with the user’s JWT for service-to-service calls.
The intention was not to add this functionality to the new client, because it was thought that the client credentials token should be used instead.
If feels like we should have an ADR that clarifies what should be used where, and potentially enhances the client if we wish to allow for other ways of using it.
The client also provided shared observability, but that only works when it is used.To be considered.
https://github.com/openedx/edx-platform/issues/32343
Requires working in Prospectus, edx.org’s private marketing site, so this is not a good candidate for community work.
(“unfinished”)Jira Legacy server System JIRA serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key ARCHBOM-1077 Related?
(“unfinished”)Jira Legacy server System JIRA serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key ARCHBOM-1168
https://github.com/openedx/edx-rest-api-client/issues/277
https://github.com/openedx/edx-drf-extensions/issues/284
...