agrc / agrc/serverless-print-proxy
Does not work as default print service for Portal
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
When I attempt to use print proxy as the default print service for portal, it fails to append the token to it and the request fails.
I can manually add a token but then, I assume, that it will be hard-coded and eventually fail after it expires. The portal website seems to automatically add the token to requests that use the same origin as the portal but not others.
I'm not sure if there is a way around this issue. Maybe it's not a huge deal since I haven't had anyone complain about it. We may just need to add a disclaimer to the readme that states that this project does not support acting as the default print service for portal.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reproducing Portal's default print-service request and compare it with a request where the token is manually added; determine whether token injection is feasible without hard-coding an expiring token. Done should be either a supported fix with coverage or a documented limitation in the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100