Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MXRestClient: Move IS API to its own #2647

Closed
3 tasks
manuroe opened this issue Aug 14, 2019 · 0 comments
Closed
3 tasks

MXRestClient: Move IS API to its own #2647

manuroe opened this issue Aug 14, 2019 · 0 comments
Assignees
@SBiOSoftWhare
Labels
A-Identity-Server feature privacy privacy-sprint T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@manuroe
Copy link
Member

manuroe commented Aug 14, 2019 •
edited

MXRestClient currently makes calls to HS, IS and AV scanner servers.
We should split it into different classes:

  • Keep MXRestClient to use the HS CS API only
  • A new MXIdentityServerRestClient or MXISRestClient class to manage call to the IS API
  • A new MXAVScannerRestClient. But this is optional and not blocking for the moment

Then:

  • We also need a new class MXIdentityServerService or stg to proxy all calls to MXISRestClient. One goal is to manage the IS access token introduced in IS API v2.

This task is prerequisite for #2603
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SBiOSoftWhare SBiOSoftWhare

Labels
A-Identity-Server feature privacy privacy-sprint T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kittykat @SBiOSoftWhare @manuroe