Repository navigation
Can an integration package serve its own routes under /eve/v1/? #5886
Replies: 1 comment
|
Hey @alliehowe29, hope you're doing well! Really nice to see the Keycard adapter, and the README section on confidential clients made the constraint very clear, thank you. I looked through main to see what's there today, in case it helps the maintainers weigh the options:
That makes me wonder if the need is wider than Keycard. Any confidential OAuth client used with Would that cover your case, or does Keycard need routes beyond the callback? And maintainers, does carrying the attempt token in |
Uh oh!
There was an error while loading. Please reload this page.
We'd like our @keycardai/eve adapter to serve its sign-in callback at
/eve/v1/keycard/callback, next to eve's own connection callbacks, so it works on every eve host with no routing setup. However your docs reserve/eve/v1/*. Outside/eve/v1/*, withEve and the Next rewrites forward nothing today, so every customer would have to add a host rule.How would you like a third-party package to handle this?
(a) Bless a vendor subtree, such as
/eve/v1/ext/<vendor>/*or/eve/v1/keycard/*.(b) Offer a supported way for an integration package to register routes that get eve's host forwarding.
(c) Something else you'd recommend.
All reactions