Replies: 1 comment 2 replies
|
I'm not sure what the ask is exactly? We do have an API, and authorized users can generate API keys. I'm not sure why you'd need/want the browser involved though? https://snipe-it.readme.io/reference |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We’re using Snipe-IT and it’s working really well for our environment.
I’m looking to automate printing asset labels using a script that controls a headless browser. Ideally, I’d like to authenticate the browser session using an API key or another long-lived token, rather than relying on a user login.
The goal is to authenticate programmatically, then navigate directly to the label page and trigger printing:
https://snipe.company.local/hardware/XXXX/label
Is there a supported way to authenticate web requests using an API key (for example, via an HTTP header or bearer token) so the browser session is considered authenticated?
I’d prefer not to rely on session cookies, as they eventually expire, and our instance uses SAML authentication, which makes automated login more complicated.
All reactions