Is EBSCOhost Passport ™ safe?
EBSCOhost Passport embeds an EBSCO OAuth client secret and sends it to EBSCO's token endpoint.
During DOI entitlement and resolver-link checks, the extension builds a client-credentials OAuth request using a bundled client_id and client_secret. It POSTs those credentials to https://ebscois-live.apigee.net/oauth-proxy/token before using the returned access token for EBSCO lookups.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itEBSCO Information Services - no other listings under this identity, 2 shared hostnames
EBSCO Information Services - no other listings under this identity, 2 shared hostnames
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 2 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 1.1.8. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on every site you visit
<all_urls>
Store data in your browser
storage
Where it sends data
Destinations our analysis observed EBSCOhost Passport ™ contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- ebscois-live.apigee.net
EBSCOhost Passport ™ sends data to ebscois-live.apigee.net. No other extension we have analysed sends data here.