Make igv web app use current google identity rather than prompting

97 views
Skip to first unread message

bhand...@gmail.com

unread,
Nov 17, 2021, 9:52:47 PM11/17/21
to igv-help
I am implementing a simple web interface for rapidly viewing regions of interest in cram/bam files using the igv web app. I am currently linking to https://igv.org/app directly, using the query string to indicate the URL of the cram file of interest, which is stored in the google cloud and is access controlled. I prefer to use the web app, rather than embedding igv.js, because that way I get the full functionality of the menus, etc.

This is working fine, except for one annoying feature. When I click on a link, I get a popup asking me to "sign in to google / choose an account". This is not too annoying the first time, and critical if I need to authenticate, but I need to do it every single time I click on a link. Note that I am usually not authenticating. My browser (chrome) already knows I am authenticated, it is just asking me to choose which google account to use. For many google apps, I don't need to do this. They simply default to the current google account / profile of the chrome window.

Is there some simple trick I can use to have igv use the google identity currently associated with my window? Or some other way to use the full igv web app functionality without this annoying popup?

Thanks,
Bob Handsaker

James Robinson

unread,
Nov 18, 2021, 12:21:49 AM11/18/21
to igv-help
Not that I'm aware of.  By using a link and query string you are reloading the webapp every time you click.  This completely resets IGV's state, including the oAuth token.  I would suggest you install your own copy of IGV-Webapp, its quite easy, and put your google files in the track menu, again which is easily customizable.   The readme at httsp://github.com/igvteam/igv-webapp has instructions for doing both.   All of our track menus are included in the download as json files which you can use to start.

It's important to note  that igv-webapp is 100% client html and javascript, in other words it is just static files,  there are no "server" requirements other than hosting a static file.   On the website we have an example of doing this in an S3 bucket.

Jim
Reply all
Reply to author
Forward
Message has been deleted
Message has been deleted
0 new messages