Hello @cmdcolin,
We are deploying JBrowse2 @umccr, primarily for the htsget support, so that different web-based clients work fine using one data access interface (htsget).
Unfortunately we hit a snag with the Bearer token support, which would allow our users to access private data via htsget, namely:
|
const base = `${this.baseUrl}/${this.trackId}` |
|
const url = `${base}?referenceName=${chr}&start=${min}&end=${max}&format=BAM` |
|
const chrId = this.chrToIndex && this.chrToIndex[chr] |
|
const result = await fetch(url, { ...opts }) |
Do you have plans to add Bearer token support to htsget in JBrowse2?
@andrewpatto @victorskl @mmalenic
/cc @ohofmann @mlin
Hello @cmdcolin,
We are deploying JBrowse2 @umccr, primarily for the htsget support, so that different web-based clients work fine using one data access interface (htsget).
Unfortunately we hit a snag with the Bearer token support, which would allow our users to access private data via htsget, namely:
bam-js/src/htsget.ts
Lines 65 to 68 in 25ba6e8
Do you have plans to add Bearer token support to htsget in JBrowse2?
@andrewpatto @victorskl @mmalenic
/cc @ohofmann @mlin