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.

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

add backend ee route to hit HM #38197

Closed
Tracked by #36367
dpsutton opened this issue Jan 26, 2024 · 0 comments · Fixed by #38153
Closed
Tracked by #36367

add backend ee route to hit HM #38197

dpsutton opened this issue Jan 26, 2024 · 0 comments · Fixed by #38153
Assignees

Comments

@dpsutton
Copy link
Contributor

dpsutton commented Jan 26, 2024

Expose an endpoint in an enterprise route that will hit HM, authenticate with email, token, and possibly version(?) to proxy to the FE.

Needs to cache the response. Not exactly clear on how long but on the magnitude of hours seems right.

Handle:

  • 200 response
  • 500 response
  • expired token
  • unrecognized token

Decisions we can make in the future (or now):

  • can we send the version the FE expects to HM and it can always speak that version?
  • if not, if HM responds with a higher version should MB not return any info? Or return a version that the FE won't speak?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants